Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d304a5acebd784660a3435af355ddd0878daa7f847aa9ad50fa681b4cc03e09b

Tx prefix hash: 5f3e1792541a2344db59e769202bd5b985795cf55eb88d811663e20cbe2abf44
Tx public key: c9099321fe5a5d4e0c434b9c15bce954fa91ed3278bce5f2bb9fad5c85bceeb4
Timestamp: 1727429715 Timestamp [UCT]: 2024-09-27 09:35:15 Age [y:d:h:m:s]: 00:105:03:35:18
Block: 1119160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75170 RingCT/type: yes/0
Extra: 01c9099321fe5a5d4e0c434b9c15bce954fa91ed3278bce5f2bb9fad5c85bceeb402110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7ee07a9d1acb16b4f6496b7d2d044893e852d6af6e1fba958bad7219fb54992 0.600000000000 1600615 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": 1119170, "vin": [ { "gen": { "height": 1119160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7ee07a9d1acb16b4f6496b7d2d044893e852d6af6e1fba958bad7219fb54992" } } ], "extra": [ 1, 201, 9, 147, 33, 254, 90, 93, 78, 12, 67, 75, 156, 21, 188, 233, 84, 250, 145, 237, 50, 120, 188, 229, 242, 187, 159, 173, 92, 133, 188, 238, 180, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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