Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ed5b142b2cdfd3f51e3b4e386dd18319c43832b4f2780a9ffbe51131706a81d

Tx prefix hash: 95ccc7e060368f6550fd7af82205badbce152a4b782879a3a582a552d833ce9f
Tx public key: 8e280aa7dcf283b5de99952eef93c5063882d50bd4192aced85b6b0ae92daff6
Timestamp: 1576427376 Timestamp [UCT]: 2019-12-15 16:29:36 Age [y:d:h:m:s]: 04:339:17:53:41
Block: 27811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128524 RingCT/type: yes/0
Extra: 018e280aa7dcf283b5de99952eef93c5063882d50bd4192aced85b6b0ae92daff6021100000003ad433a0b000000000000000000

1 output(s) for total of 496.422523127000 dcy

stealth address amount amount idx
00: de92f7f02ec72f2d48409439d31aebcff12eb4655d33fba760392fa889ef951d 496.422523127000 45867 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": 27821, "vin": [ { "gen": { "height": 27811 } } ], "vout": [ { "amount": 496422523127, "target": { "key": "de92f7f02ec72f2d48409439d31aebcff12eb4655d33fba760392fa889ef951d" } } ], "extra": [ 1, 142, 40, 10, 167, 220, 242, 131, 181, 222, 153, 149, 46, 239, 147, 197, 6, 56, 130, 213, 11, 212, 25, 42, 206, 216, 91, 107, 10, 233, 45, 175, 246, 2, 17, 0, 0, 0, 3, 173, 67, 58, 11, 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