Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60a73c8b696d5aa5e60d3dcae31ccf00cded83786bb4163f28713ed1a88abec3

Tx prefix hash: 6ef84f101325facc294297445423ec9f68556d103204d2ff49b3020b150fb803
Tx public key: 07a45fd06acb69a9596d597d9ec569a50d328b2b95c2a1cb3a75b6b4b0bad97a
Timestamp: 1583528423 Timestamp [UCT]: 2020-03-06 21:00:23 Age [y:d:h:m:s]: 04:293:15:57:01
Block: 77570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1104604 RingCT/type: yes/0
Extra: 0107a45fd06acb69a9596d597d9ec569a50d328b2b95c2a1cb3a75b6b4b0bad97a0211000000094ac5aa02000000000000000000

1 output(s) for total of 339.608993492000 dcy

stealth address amount amount idx
00: dfe4d31a54a0c4c4f6bdb8223e5b6a9ab57b23f5193b79a7f3350644269298dc 339.608993492000 142711 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": 77580, "vin": [ { "gen": { "height": 77570 } } ], "vout": [ { "amount": 339608993492, "target": { "key": "dfe4d31a54a0c4c4f6bdb8223e5b6a9ab57b23f5193b79a7f3350644269298dc" } } ], "extra": [ 1, 7, 164, 95, 208, 106, 203, 105, 169, 89, 109, 89, 125, 158, 197, 105, 165, 13, 50, 139, 43, 149, 194, 161, 203, 58, 117, 182, 180, 176, 186, 217, 122, 2, 17, 0, 0, 0, 9, 74, 197, 170, 2, 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