Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00ebaef052b5e6a21083989778e41362aa4a67da380e48f1f9777211ee0eb69d

Tx prefix hash: 78890c85c069f68764ff5e1367a2b0d635aa76638a5fd0ca1cf84fe3a2172e3d
Tx public key: f9b21fe9b42b8252e701feadf9f0ce595806dc31d756fb09653b9c3d5871f347
Timestamp: 1720778323 Timestamp [UCT]: 2024-07-12 09:58:43 Age [y:d:h:m:s]: 00:251:00:44:00
Block: 1064019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179351 RingCT/type: yes/0
Extra: 01f9b21fe9b42b8252e701feadf9f0ce595806dc31d756fb09653b9c3d5871f34702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74c6cf9a0f1d277d29bbd04fcfac57fa1bb8ad892a32cedfaf75ca60ba2970a1 0.600000000000 1534540 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": 1064029, "vin": [ { "gen": { "height": 1064019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74c6cf9a0f1d277d29bbd04fcfac57fa1bb8ad892a32cedfaf75ca60ba2970a1" } } ], "extra": [ 1, 249, 178, 31, 233, 180, 43, 130, 82, 231, 1, 254, 173, 249, 240, 206, 89, 88, 6, 220, 49, 215, 86, 251, 9, 101, 59, 156, 61, 88, 113, 243, 71, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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