Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ea98adbf64c23e7ab0cee0fea3f8769b1d55c583f49984a7e1b054157759bf9

Tx prefix hash: cacf1bd3e02ffa76557e9127b28e00d7ec6c04ebe66ddb3e49766cdbf204429c
Tx public key: 60bce8f813258f469641691c6ee40e888f7ee48ee887f5307b1b294c6000d2b4
Timestamp: 1606706640 Timestamp [UCT]: 2020-11-30 03:24:00 Age [y:d:h:m:s]: 04:176:14:53:58
Block: 152562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1137502 RingCT/type: yes/0
Extra: 0160bce8f813258f469641691c6ee40e888f7ee48ee887f5307b1b294c6000d2b4021100000037508974f9000000000000000000

1 output(s) for total of 191.645865127000 dcy

stealth address amount amount idx
00: bb134a57a42b05f390843c6797b9e4b280bc3f6a142db04c30e685dc6ed02df6 191.645865127000 253543 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": 152572, "vin": [ { "gen": { "height": 152562 } } ], "vout": [ { "amount": 191645865127, "target": { "key": "bb134a57a42b05f390843c6797b9e4b280bc3f6a142db04c30e685dc6ed02df6" } } ], "extra": [ 1, 96, 188, 232, 248, 19, 37, 143, 70, 150, 65, 105, 28, 110, 228, 14, 136, 143, 126, 228, 142, 232, 135, 245, 48, 123, 27, 41, 76, 96, 0, 210, 180, 2, 17, 0, 0, 0, 55, 80, 137, 116, 249, 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