Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cded1d36b3424ba0b3d307f0640e422b4a737f1aa7f0a052c04b5021be6b377

Tx prefix hash: dd7788b5e46603e9ce2a1ccb2328082c06822bebb888ef702eaaa468b2d7566e
Tx public key: 4ab3b42be0f63bfa86392a068550904f545ac22dd0517d2e54b9a71aabff7719
Timestamp: 1713826129 Timestamp [UCT]: 2024-04-22 22:48:49 Age [y:d:h:m:s]: 00:206:11:48:55
Block: 1006371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147821 RingCT/type: yes/0
Extra: 014ab3b42be0f63bfa86392a068550904f545ac22dd0517d2e54b9a71aabff771902110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c97e390583526675b78d8dd0e66c19f485ef9a7cd6baae0a22b23e3e3e5af31e 0.600000000000 1467385 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": 1006381, "vin": [ { "gen": { "height": 1006371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c97e390583526675b78d8dd0e66c19f485ef9a7cd6baae0a22b23e3e3e5af31e" } } ], "extra": [ 1, 74, 179, 180, 43, 224, 246, 59, 250, 134, 57, 42, 6, 133, 80, 144, 79, 84, 90, 194, 45, 208, 81, 125, 46, 84, 185, 167, 26, 171, 255, 119, 25, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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