Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80d06795f7fb55a5b188afd4f1caadf535e83c93ea729a1efd33304afa8537ef

Tx prefix hash: a856e4efecafbf31f933aa768879bbb29a0747e04d849cbd0172c768ea31a187
Tx public key: a8ab853e7238246e65218cdae6105d95fda749f12fe79b171cb7e7111c5ca750
Timestamp: 1579006033 Timestamp [UCT]: 2020-01-14 12:47:13 Age [y:d:h:m:s]: 04:350:06:34:22
Block: 45257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1139953 RingCT/type: yes/0
Extra: 01a8ab853e7238246e65218cdae6105d95fda749f12fe79b171cb7e7111c5ca750021100000047ff58ae94000000000000000000

1 output(s) for total of 434.555861083000 dcy

stealth address amount amount idx
00: 47b3e63847807231d8b3a32837551af3a90175373b9b0f6a6e76eceb5d0266c9 434.555861083000 82635 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": 45267, "vin": [ { "gen": { "height": 45257 } } ], "vout": [ { "amount": 434555861083, "target": { "key": "47b3e63847807231d8b3a32837551af3a90175373b9b0f6a6e76eceb5d0266c9" } } ], "extra": [ 1, 168, 171, 133, 62, 114, 56, 36, 110, 101, 33, 140, 218, 230, 16, 93, 149, 253, 167, 73, 241, 47, 231, 155, 23, 28, 183, 231, 17, 28, 92, 167, 80, 2, 17, 0, 0, 0, 71, 255, 88, 174, 148, 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