Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96a8405c1f4a9d2c46f79eeb59ee0a37856bad30bcf4aaec7d1aa48186b87489

Tx prefix hash: 8a76d1532a027de8f674431edd996aa123f4ec18752d21ce3d6934ed85317088
Tx public key: bf12c55652c02c4ab685ca4b5e435a61e905eaa56a39466e671e30d654ee132d
Timestamp: 1707993630 Timestamp [UCT]: 2024-02-15 10:40:30 Age [y:d:h:m:s]: 01:058:11:39:21
Block: 958018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302851 RingCT/type: yes/0
Extra: 01bf12c55652c02c4ab685ca4b5e435a61e905eaa56a39466e671e30d654ee132d0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3aa00e697e286bb5ff05e6b69b360c8eb6f9fac5a284ab5c2850c23674f4e2f9 0.600000000000 1417369 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": 958028, "vin": [ { "gen": { "height": 958018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3aa00e697e286bb5ff05e6b69b360c8eb6f9fac5a284ab5c2850c23674f4e2f9" } } ], "extra": [ 1, 191, 18, 197, 86, 82, 192, 44, 74, 182, 133, 202, 75, 94, 67, 90, 97, 233, 5, 234, 165, 106, 57, 70, 110, 103, 30, 48, 214, 84, 238, 19, 45, 2, 17, 0, 0, 0, 1, 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