Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd46e898293aa935ac48b9d906f0974c0a04e2955bd1f1556e37a60734409ce0

Tx prefix hash: b556b5ab75712e8cd1bab2c90c2ea00060811767d4924da57e0ce818ec2209e9
Tx public key: 4762e5605115a34b8c50f051b6f71eaed7665df9244b4eda7c1202b3f27010f0
Timestamp: 1737432087 Timestamp [UCT]: 2025-01-21 04:01:27 Age [y:d:h:m:s]: 00:334:21:40:56
Block: 1201882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236955 RingCT/type: yes/0
Extra: 014762e5605115a34b8c50f051b6f71eaed7665df9244b4eda7c1202b3f27010f00211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0e251c96b18fc93a9c02d0d42bd34f305b40f5bc557f7618b894e1a42da6a23 0.600000000000 1688539 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": 1201892, "vin": [ { "gen": { "height": 1201882 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0e251c96b18fc93a9c02d0d42bd34f305b40f5bc557f7618b894e1a42da6a23" } } ], "extra": [ 1, 71, 98, 229, 96, 81, 21, 163, 75, 140, 80, 240, 81, 182, 247, 30, 174, 215, 102, 93, 249, 36, 75, 78, 218, 124, 18, 2, 179, 242, 112, 16, 240, 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