Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03bf01c8a586822038e0f7d27fff8db381f9fe8b07ca74afa5bff88f1fa1cea8

Tx prefix hash: 360e224ff9c3bde724ee5d54733381acfd1fd29fbcad8640e10f11c079528739
Tx public key: a4d0c3c73fd51f1b5fb3c8ddd23cf865ff79851ccd78310cd6378d0f6384034e
Timestamp: 1697413591 Timestamp [UCT]: 2023-10-15 23:46:31 Age [y:d:h:m:s]: 01:096:05:19:40
Block: 870504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329982 RingCT/type: yes/0
Extra: 01a4d0c3c73fd51f1b5fb3c8ddd23cf865ff79851ccd78310cd6378d0f6384034e02110000000b75e3f0e9000000000000000000

1 output(s) for total of 0.801048684000 dcy

stealth address amount amount idx
00: 1ca2ced19496ef67e876d400ed3387ee3f24318640d6bbaaab46d51cce4b7614 0.801048684000 1325383 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": 870514, "vin": [ { "gen": { "height": 870504 } } ], "vout": [ { "amount": 801048684, "target": { "key": "1ca2ced19496ef67e876d400ed3387ee3f24318640d6bbaaab46d51cce4b7614" } } ], "extra": [ 1, 164, 208, 195, 199, 63, 213, 31, 27, 95, 179, 200, 221, 210, 60, 248, 101, 255, 121, 133, 28, 205, 120, 49, 12, 214, 55, 141, 15, 99, 132, 3, 78, 2, 17, 0, 0, 0, 11, 117, 227, 240, 233, 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