Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8e27387c6bfd80f73eb7a2f53cb596b5f5f0f450ce00724637f95a6f649ccff

Tx prefix hash: 854fff4965239afb323edcfe2c632348899fb907dc629d92fd59ec2c487491aa
Tx public key: 14d9c61c202deea2f57f9f2deb7fc99deddebe21ad86b32d0d3ba3e478dd8055
Timestamp: 1711296943 Timestamp [UCT]: 2024-03-24 16:15:43 Age [y:d:h:m:s]: 01:062:07:33:51
Block: 985422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305534 RingCT/type: yes/0
Extra: 0114d9c61c202deea2f57f9f2deb7fc99deddebe21ad86b32d0d3ba3e478dd80550211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1d9e00de7e703a1a4264a5be5268c22d14d26dc66763f35ffde60eaad364cc0 0.600000000000 1445633 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": 985432, "vin": [ { "gen": { "height": 985422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1d9e00de7e703a1a4264a5be5268c22d14d26dc66763f35ffde60eaad364cc0" } } ], "extra": [ 1, 20, 217, 198, 28, 32, 45, 238, 162, 245, 127, 159, 45, 235, 127, 201, 157, 237, 222, 190, 33, 173, 134, 179, 45, 13, 59, 163, 228, 120, 221, 128, 85, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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