Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bed7ba9c3ae0ec6bf83b8eefaaf70c76162d7f932166ef7e29476222eb7f6ea

Tx prefix hash: a9f30f5c3a0730d540785c25b57a07f2ee9f07bead04c98e4183e5277e028dd9
Tx public key: 5c74fd79992e5c2d7d967872553ef9236376a128f698ba8a7560afb15ef72642
Timestamp: 1626769772 Timestamp [UCT]: 2021-07-20 08:29:32 Age [y:d:h:m:s]: 03:229:11:01:19
Block: 297465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 935417 RingCT/type: yes/0
Extra: 015c74fd79992e5c2d7d967872553ef9236376a128f698ba8a7560afb15ef72642021100000008d2fc4d28000000000000000000

1 output(s) for total of 63.442895490000 dcy

stealth address amount amount idx
00: cf44f7cb6b61e77ab10192f8b342c562c67c7c5441143e10e73420e4f1764715 63.442895490000 622569 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": 297475, "vin": [ { "gen": { "height": 297465 } } ], "vout": [ { "amount": 63442895490, "target": { "key": "cf44f7cb6b61e77ab10192f8b342c562c67c7c5441143e10e73420e4f1764715" } } ], "extra": [ 1, 92, 116, 253, 121, 153, 46, 92, 45, 125, 150, 120, 114, 85, 62, 249, 35, 99, 118, 161, 40, 246, 152, 186, 138, 117, 96, 175, 177, 94, 247, 38, 66, 2, 17, 0, 0, 0, 8, 210, 252, 77, 40, 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