Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b5a1ce9ed6b812185a4a0a986230a8534679921ee977905a348e3dc075db59c

Tx prefix hash: d58ea408c54c86eb43ad74082cebdcc93994f65267c9016dd08e6b33324a27b4
Tx public key: 01ec3c25a8f70bc7bd61f820a40f3306992ab2dc3b691028c801cdd2e9f9d3ea
Timestamp: 1730910353 Timestamp [UCT]: 2024-11-06 16:25:53 Age [y:d:h:m:s]: 00:364:18:34:58
Block: 1147923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258233 RingCT/type: yes/0
Extra: 0101ec3c25a8f70bc7bd61f820a40f3306992ab2dc3b691028c801cdd2e9f9d3ea021100000002007f978a000000000000000000

1 output(s) for total of 0.600200000000 dcy

stealth address amount amount idx
00: 52f695cbfc16439092121870682b3414cbc1461a4d8ebc195a82b16331452853 0.600200000000 1632636 of 0

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": 1147933, "vin": [ { "gen": { "height": 1147923 } } ], "vout": [ { "amount": 600200000, "target": { "key": "52f695cbfc16439092121870682b3414cbc1461a4d8ebc195a82b16331452853" } } ], "extra": [ 1, 1, 236, 60, 37, 168, 247, 11, 199, 189, 97, 248, 32, 164, 15, 51, 6, 153, 42, 178, 220, 59, 105, 16, 40, 200, 1, 205, 210, 233, 249, 211, 234, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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