Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: e5f9e67c2a44b48fd97a01f480234c272247dd826e83138fa1a9c2fe714cde11

Tx prefix hash: 974cce070b7ef3eea6e4384f423f3a1bf75437f2768dabe7413941138252588a
Tx public key: 6d926d473af53d2e06d700e56d216de90d533561a3a9553b7b8f67e58bb199b2
Timestamp: 1696885265 Timestamp [UCT]: 2023-10-09 21:01:05 Age [y:d:h:m:s]: 02:028:15:44:46
Block: 866128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 540078 RingCT/type: yes/0
Extra: 016d926d473af53d2e06d700e56d216de90d533561a3a9553b7b8f67e58bb199b202110000000875e3f0e9000000000000000000

1 output(s) for total of 0.828244236000 dcy

stealth address amount amount idx
00: 95716d2b7a1e4c8da5d12ebde0591e941ccd0533827eea6aae554aefc7ccb977 0.828244236000 1320700 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 866138, "vin": [ { "gen": { "height": 866128 } } ], "vout": [ { "amount": 828244236, "target": { "key": "95716d2b7a1e4c8da5d12ebde0591e941ccd0533827eea6aae554aefc7ccb977" } } ], "extra": [ 1, 109, 146, 109, 71, 58, 245, 61, 46, 6, 215, 0, 229, 109, 33, 109, 233, 13, 83, 53, 97, 163, 169, 85, 59, 123, 143, 103, 229, 139, 177, 153, 178, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8