Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4c49dea7d09eb75739a5a90dc4bacbe8ceef1dc2441d78ca18402a805e73ba0

Tx prefix hash: 89dd1f1b4d32ddd9fee991eb65ff065c5f081b34e4f190210c8a459f05da1e59
Tx public key: 18dc0bde368efe3999e5548d2a8cbf5a6c2651e8dcd00ae47d6ec81a497c6c25
Timestamp: 1712623525 Timestamp [UCT]: 2024-04-09 00:45:25 Age [y:d:h:m:s]: 01:226:14:41:04
Block: 996373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420660 RingCT/type: yes/0
Extra: 0118dc0bde368efe3999e5548d2a8cbf5a6c2651e8dcd00ae47d6ec81a497c6c2502110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e251ba5f616cc3cb95ed774cc2cf43f0b191d64a259b64b39a071b2e114dc9f 0.600000000000 1456791 of 15

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": 996383, "vin": [ { "gen": { "height": 996373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e251ba5f616cc3cb95ed774cc2cf43f0b191d64a259b64b39a071b2e114dc9f" } } ], "extra": [ 1, 24, 220, 11, 222, 54, 142, 254, 57, 153, 229, 84, 141, 42, 140, 191, 90, 108, 38, 81, 232, 220, 208, 10, 228, 125, 110, 200, 26, 73, 124, 108, 37, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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