Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5228a1840414a470a8ad17011d48daee338b148aadc6ccbdab3b74a58e01da4

Tx prefix hash: ab432644a987da01e5a297398b7c9ec5543e1476bd93bb96f98c932da69c5d8c
Tx public key: b3a85abc6b430281c5a0da1c2ced497cd4eefe441a09687cfa0fbb96bc15c629
Timestamp: 1708305549 Timestamp [UCT]: 2024-02-19 01:19:09 Age [y:d:h:m:s]: 01:070:10:32:38
Block: 960597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311407 RingCT/type: yes/0
Extra: 01b3a85abc6b430281c5a0da1c2ced497cd4eefe441a09687cfa0fbb96bc15c6290211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5a547959b5aae032cd0aadf9a217f8832ed4df7c9965a36b8a7cf681d3b0eaf 0.600000000000 1420182 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": 960607, "vin": [ { "gen": { "height": 960597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5a547959b5aae032cd0aadf9a217f8832ed4df7c9965a36b8a7cf681d3b0eaf" } } ], "extra": [ 1, 179, 168, 90, 188, 107, 67, 2, 129, 197, 160, 218, 28, 44, 237, 73, 124, 212, 238, 254, 68, 26, 9, 104, 124, 250, 15, 187, 150, 188, 21, 198, 41, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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