Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 159b61e775e626fab514b04cfee82996eebc460d0ad29a6ff2ea4150d87c2b07

Tx prefix hash: c309a44bdf3270840c97d3d7f347676aa46237f258b55f331f0036dccaed7e6a
Tx public key: 0af08121923c0f7bef680e599dd65e0b78c14c7f4f09d6c0d3548c17408a5fd3
Timestamp: 1716159495 Timestamp [UCT]: 2024-05-19 22:58:15 Age [y:d:h:m:s]: 00:248:15:29:46
Block: 1025718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177907 RingCT/type: yes/0
Extra: 010af08121923c0f7bef680e599dd65e0b78c14c7f4f09d6c0d3548c17408a5fd302110000000e59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f451e0b14e5f8fb202aa4037ef3507965195f6ffde4a7a80b09ba713df61e09 0.600000000000 1492407 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": 1025728, "vin": [ { "gen": { "height": 1025718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f451e0b14e5f8fb202aa4037ef3507965195f6ffde4a7a80b09ba713df61e09" } } ], "extra": [ 1, 10, 240, 129, 33, 146, 60, 15, 123, 239, 104, 14, 89, 157, 214, 94, 11, 120, 193, 76, 127, 79, 9, 214, 192, 211, 84, 140, 23, 64, 138, 95, 211, 2, 17, 0, 0, 0, 14, 89, 218, 211, 245, 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