Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dc36e0056fd1f3bb4b1b6fcb7d186997e5798c7106c4ee859d2f9c126e40724

Tx prefix hash: d4080503aba6a79ffd3ed3d49467c8a9ee1ed7c0eb9dddcc10d348f0ead4b8cf
Tx public key: 396cee500903e6f940de16832c51efabe8a1d2f8dbeae7f0decf582982b9ba27
Timestamp: 1732444568 Timestamp [UCT]: 2024-11-24 10:36:08 Age [y:d:h:m:s]: 00:000:06:46:48
Block: 1160626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203 RingCT/type: yes/0
Extra: 01396cee500903e6f940de16832c51efabe8a1d2f8dbeae7f0decf582982b9ba27021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 626f591ca40e62bd9554e52653781000ad1358af7f5f9e5db0fc46107611f735 0.600000000000 1646273 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": 1160636, "vin": [ { "gen": { "height": 1160626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "626f591ca40e62bd9554e52653781000ad1358af7f5f9e5db0fc46107611f735" } } ], "extra": [ 1, 57, 108, 238, 80, 9, 3, 230, 249, 64, 222, 22, 131, 44, 81, 239, 171, 232, 161, 210, 248, 219, 234, 231, 240, 222, 207, 88, 41, 130, 185, 186, 39, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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