Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 832a5a0df3fb449b457b5da87e1a62e851b79d9a281fef22ef441480c50e4f3c

Tx prefix hash: a834820a64ce3ab531cb64b8c16cbc43e6551792823162a29147ec2c564c602b
Tx public key: f807c230debc5baaae668ff000cd6554e5d35f6b68fc81510554a97d217c2973
Timestamp: 1713955098 Timestamp [UCT]: 2024-04-24 10:38:18 Age [y:d:h:m:s]: 00:261:13:08:41
Block: 1007441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187201 RingCT/type: yes/0
Extra: 01f807c230debc5baaae668ff000cd6554e5d35f6b68fc81510554a97d217c29730211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a3ceb2ab242ae61b3e098b0509164c4feb00154079f8ff432b219d922ef8cf3 0.600000000000 1468781 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": 1007451, "vin": [ { "gen": { "height": 1007441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a3ceb2ab242ae61b3e098b0509164c4feb00154079f8ff432b219d922ef8cf3" } } ], "extra": [ 1, 248, 7, 194, 48, 222, 188, 91, 170, 174, 102, 143, 240, 0, 205, 101, 84, 229, 211, 95, 107, 104, 252, 129, 81, 5, 84, 169, 125, 33, 124, 41, 115, 2, 17, 0, 0, 0, 5, 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