Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0760369dc9d50508dc2fbd4f7a8b6ae89f5a3ec3dfc47f375b001a9b7aa97df1

Tx prefix hash: 953830796b70c6b5e62d7543ae9092358f4382fb97c8576d1441dc9b19765f6a
Tx public key: e187e5b4b0d513ff1cc37bbbcd6108f7c883b25b7c25afefcc5806ced474f964
Timestamp: 1699310909 Timestamp [UCT]: 2023-11-06 22:48:29 Age [y:d:h:m:s]: 01:183:06:05:27
Block: 886041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392166 RingCT/type: yes/0
Extra: 01e187e5b4b0d513ff1cc37bbbcd6108f7c883b25b7c25afefcc5806ced474f96402110000000533af99f4000000000000000000

1 output(s) for total of 0.711505658000 dcy

stealth address amount amount idx
00: 07f3003c3e6c11283e3a8580e594d20878a42fc82a11103ae5d94746dd6b543c 0.711505658000 1341846 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": 886051, "vin": [ { "gen": { "height": 886041 } } ], "vout": [ { "amount": 711505658, "target": { "key": "07f3003c3e6c11283e3a8580e594d20878a42fc82a11103ae5d94746dd6b543c" } } ], "extra": [ 1, 225, 135, 229, 180, 176, 213, 19, 255, 28, 195, 123, 187, 205, 97, 8, 247, 200, 131, 178, 91, 124, 37, 175, 239, 204, 88, 6, 206, 212, 116, 249, 100, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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