Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b43d6da39b73a993fbc8012b5aa390b64381a4eaca0b0773e83017cecb09d15e

Tx prefix hash: 7f4a1f35bc48a9e3ee764e820efa5b4bfd6366dae762a0177a4a26ee0da7076e
Tx public key: 1eb8010f5c16c41c2fe90406eb3f28d34992c74dffdd7e96c91302b97f199e8c
Timestamp: 1737711993 Timestamp [UCT]: 2025-01-24 09:46:33 Age [y:d:h:m:s]: 00:144:06:35:00
Block: 1204204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102858 RingCT/type: yes/0
Extra: 011eb8010f5c16c41c2fe90406eb3f28d34992c74dffdd7e96c91302b97f199e8c0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93814404ab862d18cac0b74eb5d6ec34d6646d462e1fc3317658294c7734f22c 0.600000000000 1690889 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": 1204214, "vin": [ { "gen": { "height": 1204204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93814404ab862d18cac0b74eb5d6ec34d6646d462e1fc3317658294c7734f22c" } } ], "extra": [ 1, 30, 184, 1, 15, 92, 22, 196, 28, 47, 233, 4, 6, 235, 63, 40, 211, 73, 146, 199, 77, 255, 221, 126, 150, 201, 19, 2, 185, 127, 25, 158, 140, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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