Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80d01a91d49c88352a83055c166b8564cc29aa3854c04df053c120896d673200

Tx prefix hash: bf59a7bd2587e79b233fd87d275a0d64954c504ad66433a29497cf6359c5f80a
Tx public key: 71d070fa71c6039dee89cb11d5f0633c831dba6d322043bbdb1dffd3f0a0f6fe
Timestamp: 1580979754 Timestamp [UCT]: 2020-02-06 09:02:34 Age [y:d:h:m:s]: 04:274:01:47:44
Block: 59884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1087155 RingCT/type: yes/0
Extra: 0171d070fa71c6039dee89cb11d5f0633c831dba6d322043bbdb1dffd3f0a0f6fe0211000000034943cd9f000000000000000000

1 output(s) for total of 388.669326223000 dcy

stealth address amount amount idx
00: 36dd9d0e513fbc127d6441836f79eeb9875708b6ae33c4a67a1eb8537fb8079c 388.669326223000 110424 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": 59894, "vin": [ { "gen": { "height": 59884 } } ], "vout": [ { "amount": 388669326223, "target": { "key": "36dd9d0e513fbc127d6441836f79eeb9875708b6ae33c4a67a1eb8537fb8079c" } } ], "extra": [ 1, 113, 208, 112, 250, 113, 198, 3, 157, 238, 137, 203, 17, 213, 240, 99, 60, 131, 29, 186, 109, 50, 32, 67, 187, 219, 29, 255, 211, 240, 160, 246, 254, 2, 17, 0, 0, 0, 3, 73, 67, 205, 159, 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