Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f365dd557941681fcfd71d5ef9c40c319b53461129c1fc1da52496fe42832136

Tx prefix hash: 347c4ac4168d0468f55631cf0bd6ef24305965fa093b5e83b6776422b3888eac
Tx public key: 2f0c9ef13de307af99ba1e4d4aae03e220ce58b3d18bfab1e42b74368c8ae347
Timestamp: 1696659289 Timestamp [UCT]: 2023-10-07 06:14:49 Age [y:d:h:m:s]: 01:169:09:20:49
Block: 864250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382098 RingCT/type: yes/0
Extra: 012f0c9ef13de307af99ba1e4d4aae03e220ce58b3d18bfab1e42b74368c8ae34702110000000c75e3f0e9000000000000000000

1 output(s) for total of 0.840196791000 dcy

stealth address amount amount idx
00: ef19b37d68861453bced1f14f1811cefbcc78fa4f381e2b6ee6e08f2df09cd8e 0.840196791000 1318760 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": 864260, "vin": [ { "gen": { "height": 864250 } } ], "vout": [ { "amount": 840196791, "target": { "key": "ef19b37d68861453bced1f14f1811cefbcc78fa4f381e2b6ee6e08f2df09cd8e" } } ], "extra": [ 1, 47, 12, 158, 241, 61, 227, 7, 175, 153, 186, 30, 77, 74, 174, 3, 226, 32, 206, 88, 179, 209, 139, 250, 177, 228, 43, 116, 54, 140, 138, 227, 71, 2, 17, 0, 0, 0, 12, 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