Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98ca9e1bb6595a2a3aaff8936be2bace2cdf2ef5c08ec3a512dfef00653ed12b

Tx prefix hash: 59d292ef664d8fb3635e9a65b21c4287629b610fcc9758f216af9a3f63952a63
Tx public key: 1eac70bab4b39799fc305c8f5e71c6094224d5a3906f915e5c12d9642c396d4c
Timestamp: 1715596044 Timestamp [UCT]: 2024-05-13 10:27:24 Age [y:d:h:m:s]: 00:287:18:59:19
Block: 1021064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205654 RingCT/type: yes/0
Extra: 011eac70bab4b39799fc305c8f5e71c6094224d5a3906f915e5c12d9642c396d4c02110000000139e1d5d3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 203822093dcc7357e56e7f7a3baeab55996ffce12b6207397dfc20379c475663 0.600000000000 1485249 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": 1021074, "vin": [ { "gen": { "height": 1021064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "203822093dcc7357e56e7f7a3baeab55996ffce12b6207397dfc20379c475663" } } ], "extra": [ 1, 30, 172, 112, 186, 180, 179, 151, 153, 252, 48, 92, 143, 94, 113, 198, 9, 66, 36, 213, 163, 144, 111, 145, 94, 92, 18, 217, 100, 44, 57, 109, 76, 2, 17, 0, 0, 0, 1, 57, 225, 213, 211, 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