Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6806f1261618b1423f78e7ee236dc447cc7513c2852d9adb0ad6480ac53f2569

Tx prefix hash: 3c3ba401ad26b8c59b215da7dc3510a98cf93e7287b6999fa2c73fd89e926d9f
Tx public key: 7d5c0ef82c4652b942e5007b72ba1a53573279b914e2d1aa812996c59dc700b2
Timestamp: 1577745715 Timestamp [UCT]: 2019-12-30 22:41:55 Age [y:d:h:m:s]: 04:332:01:59:28
Block: 35362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126400 RingCT/type: yes/0
Extra: 017d5c0ef82c4652b942e5007b72ba1a53573279b914e2d1aa812996c59dc700b2021100000014d81c26c0000000000000000000

1 output(s) for total of 468.631922727000 dcy

stealth address amount amount idx
00: 2973bfe1bfda23a8bd0099e0be008099bbc17646d0ff088e0bcbb84e6334172e 468.631922727000 59586 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": 35372, "vin": [ { "gen": { "height": 35362 } } ], "vout": [ { "amount": 468631922727, "target": { "key": "2973bfe1bfda23a8bd0099e0be008099bbc17646d0ff088e0bcbb84e6334172e" } } ], "extra": [ 1, 125, 92, 14, 248, 44, 70, 82, 185, 66, 229, 0, 123, 114, 186, 26, 83, 87, 50, 121, 185, 20, 226, 209, 170, 129, 41, 150, 197, 157, 199, 0, 178, 2, 17, 0, 0, 0, 20, 216, 28, 38, 192, 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