Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 160ef6bfa9e490ebb74289d3e516799e19c39e84bddc9836ab01f9b947031370

Tx prefix hash: 6aff7421e3647aea718f861ca8e4bd9043a980955e1e38de467f2d98387b9290
Tx public key: 5791d307553d9d1cc68d56695d59913d921ff94df0f3948f4b644d08e8e24db2
Timestamp: 1710697328 Timestamp [UCT]: 2024-03-17 17:42:08 Age [y:d:h:m:s]: 00:187:17:07:28
Block: 980452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134439 RingCT/type: yes/0
Extra: 015791d307553d9d1cc68d56695d59913d921ff94df0f3948f4b644d08e8e24db202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7b4d8f1a8127cc10b01986e0f42d14e8fff733aaba16a23fe0cb14dc8c469e2 0.600000000000 1440519 of 15

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": 980462, "vin": [ { "gen": { "height": 980452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7b4d8f1a8127cc10b01986e0f42d14e8fff733aaba16a23fe0cb14dc8c469e2" } } ], "extra": [ 1, 87, 145, 211, 7, 85, 61, 157, 28, 198, 141, 86, 105, 93, 89, 145, 61, 146, 31, 249, 77, 240, 243, 148, 143, 75, 100, 77, 8, 232, 226, 77, 178, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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