Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed19b532a4e1b1e6b0313309f3de61444ca83ee3ff484ebaa41c21d4eaadbfdc

Tx prefix hash: 834b1a213c45f940d9eeb035463ef610e7b427b4d5498add2032005733b9f8ba
Tx public key: d8d8d83ca47e949036d22345c7a7ccace2c7ce926d069b4fa98db28408507920
Timestamp: 1758099749 Timestamp [UCT]: 2025-09-17 09:02:29 Age [y:d:h:m:s]: 00:099:15:18:00
Block: 1370310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71338 RingCT/type: yes/0
Extra: 01d8d8d83ca47e949036d22345c7a7ccace2c7ce926d069b4fa98db28408507920021100000005b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5384f4eb4c147b846abdb4531bd21dcca00cae011fa10b96f4a25a2d9b6c97b 0.600000000000 1858385 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": 1370320, "vin": [ { "gen": { "height": 1370310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5384f4eb4c147b846abdb4531bd21dcca00cae011fa10b96f4a25a2d9b6c97b" } } ], "extra": [ 1, 216, 216, 216, 60, 164, 126, 148, 144, 54, 210, 35, 69, 199, 167, 204, 172, 226, 199, 206, 146, 109, 6, 155, 79, 169, 141, 178, 132, 8, 80, 121, 32, 2, 17, 0, 0, 0, 5, 178, 247, 132, 196, 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