Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89cc6460aa0cfd17955a3e4a2fc1aa1aa6b1a752db75e856fa02ccf7d4b0560a

Tx prefix hash: da7c3e22d273ae8f0703107c06e78dc606335d73d85bc66cd16be54a6cda9c20
Tx public key: 97a64664ff45b82cd2910ae93dee7ce47e664eb526742767dbbe2050e8f99588
Timestamp: 1574461572 Timestamp [UCT]: 2019-11-22 22:26:12 Age [y:d:h:m:s]: 05:036:21:20:00
Block: 14805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1169705 RingCT/type: yes/0
Extra: 0197a64664ff45b82cd2910ae93dee7ce47e664eb526742767dbbe2050e8f99588021100000001ccefb800000000000000000000

1 output(s) for total of 548.208510831000 dcy

stealth address amount amount idx
00: 9e2ad5d1a47de9ab9d310a767a33a79e575186c621142b61af1770a6f4e0860f 548.208510831000 19189 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": 14815, "vin": [ { "gen": { "height": 14805 } } ], "vout": [ { "amount": 548208510831, "target": { "key": "9e2ad5d1a47de9ab9d310a767a33a79e575186c621142b61af1770a6f4e0860f" } } ], "extra": [ 1, 151, 166, 70, 100, 255, 69, 184, 44, 210, 145, 10, 233, 61, 238, 124, 228, 126, 102, 78, 181, 38, 116, 39, 103, 219, 190, 32, 80, 232, 249, 149, 136, 2, 17, 0, 0, 0, 1, 204, 239, 184, 0, 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