Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bf05e51a17ceca9415494dfd3f59b438e9f02b003f7a1c1654012b0fc7e3959

Tx prefix hash: aa3e69faf55c5e2fd2600b10b293ca2bd891d095adc40d7dfa9a530884b52399
Tx public key: 5ae5346efeba95974f310651fc3b2144ce68d5a0352b577c69a741ac0fe14ada
Timestamp: 1731223833 Timestamp [UCT]: 2024-11-10 07:30:33 Age [y:d:h:m:s]: 00:140:18:49:01
Block: 1150506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100452 RingCT/type: yes/0
Extra: 015ae5346efeba95974f310651fc3b2144ce68d5a0352b577c69a741ac0fe14ada0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59e5c17b1ec5b68244a4d2c19f4177f866523c232292a6dd1f65c2756c47df5c 0.600000000000 1635845 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": 1150516, "vin": [ { "gen": { "height": 1150506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59e5c17b1ec5b68244a4d2c19f4177f866523c232292a6dd1f65c2756c47df5c" } } ], "extra": [ 1, 90, 229, 52, 110, 254, 186, 149, 151, 79, 49, 6, 81, 252, 59, 33, 68, 206, 104, 213, 160, 53, 43, 87, 124, 105, 167, 65, 172, 15, 225, 74, 218, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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