Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64542d67cfca4afe90a8a2f13472f94cfc1faa519a1228962dd923f3712d607d

Tx prefix hash: 473d986e0f0af2df1b27c3451a4d4fdc797dd825e6d2ca297a1d471c0ab82138
Tx public key: a7854ccdb7cf062df44df7d1434607bc499bbc369f0624cb3639dfa5b5415863
Timestamp: 1711313362 Timestamp [UCT]: 2024-03-24 20:49:22 Age [y:d:h:m:s]: 01:235:03:43:29
Block: 985561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426745 RingCT/type: yes/0
Extra: 01a7854ccdb7cf062df44df7d1434607bc499bbc369f0624cb3639dfa5b54158630211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f87f61b114301b4eb73c336b1068ada154a2c4c2141cf0f8e3cf9ff3fe170f72 0.600000000000 1445776 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": 985571, "vin": [ { "gen": { "height": 985561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f87f61b114301b4eb73c336b1068ada154a2c4c2141cf0f8e3cf9ff3fe170f72" } } ], "extra": [ 1, 167, 133, 76, 205, 183, 207, 6, 45, 244, 77, 247, 209, 67, 70, 7, 188, 73, 155, 188, 54, 159, 6, 36, 203, 54, 57, 223, 165, 181, 65, 88, 99, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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