Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e005345904e21e1f12d20fd374906f5dd96eb38565906264cfb80377107f1cf

Tx prefix hash: fe14f00984ea0101ca6825f62b853f0694496ae94f38d38fee2e2a4a6588a104
Tx public key: 2ae8136bc4c4090a4a2ca8fb36c1ea96e3544577d60424f0760a2346ad760c63
Timestamp: 1695465963 Timestamp [UCT]: 2023-09-23 10:46:03 Age [y:d:h:m:s]: 01:162:07:03:04
Block: 854355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377035 RingCT/type: yes/0
Extra: 012ae8136bc4c4090a4a2ca8fb36c1ea96e3544577d60424f0760a2346ad760c6302110000000e33af99f4000000000000000000

1 output(s) for total of 0.906081526000 dcy

stealth address amount amount idx
00: e3da7197df85a98988ac32726f61e06a14c0f093aa78c76da59c9336b2c0a283 0.906081526000 1308325 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": 854365, "vin": [ { "gen": { "height": 854355 } } ], "vout": [ { "amount": 906081526, "target": { "key": "e3da7197df85a98988ac32726f61e06a14c0f093aa78c76da59c9336b2c0a283" } } ], "extra": [ 1, 42, 232, 19, 107, 196, 196, 9, 10, 74, 44, 168, 251, 54, 193, 234, 150, 227, 84, 69, 119, 214, 4, 36, 240, 118, 10, 35, 70, 173, 118, 12, 99, 2, 17, 0, 0, 0, 14, 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