Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aeb80fa529bf552369d5ffcc0605f857a49a9084484040d8fd0cc7ba4e71585a

Tx prefix hash: 17140c8a46e522a417bcf4a26200a21e60e8e9b2ba6fc2345ca3a8ad00a02d21
Tx public key: ec15535929ed4f003de5eac33e7d79df6e970774575241ab024f7c79a2dadafa
Timestamp: 1580994104 Timestamp [UCT]: 2020-02-06 13:01:44 Age [y:d:h:m:s]: 05:004:06:04:57
Block: 59981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1155008 RingCT/type: yes/0
Extra: 01ec15535929ed4f003de5eac33e7d79df6e970774575241ab024f7c79a2dadafa02110000000c8a2ee0d9000000000000000000

1 output(s) for total of 388.381796304000 dcy

stealth address amount amount idx
00: db7392fdff6bbc4b17d0bf694ad3f8c11866651ba469fa323258b99ec18b8f74 388.381796304000 110621 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": 59991, "vin": [ { "gen": { "height": 59981 } } ], "vout": [ { "amount": 388381796304, "target": { "key": "db7392fdff6bbc4b17d0bf694ad3f8c11866651ba469fa323258b99ec18b8f74" } } ], "extra": [ 1, 236, 21, 83, 89, 41, 237, 79, 0, 61, 229, 234, 195, 62, 125, 121, 223, 110, 151, 7, 116, 87, 82, 65, 171, 2, 79, 124, 121, 162, 218, 218, 250, 2, 17, 0, 0, 0, 12, 138, 46, 224, 217, 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