Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 941c0d549759e6742b4035287052324b35584fefcab33ca64bf93e6623c7db0e

Tx prefix hash: a22c6d5d2c72e449e407e3a309394d5f28063682191b5ff255e707b46ead347b
Tx public key: 6c19f3350ef4da62e8414cdf24dfd0c996dc68f6f0f6692c0fee258e279060e6
Timestamp: 1755738835 Timestamp [UCT]: 2025-08-21 01:13:55 Age [y:d:h:m:s]: 00:164:09:59:02
Block: 1350960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117327 RingCT/type: yes/0
Extra: 016c19f3350ef4da62e8414cdf24dfd0c996dc68f6f0f6692c0fee258e279060e60211000000058368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efe6f2f333fee0ade5e4bfd3cc9b1773dcb31194636a5810a6c8905ef148cc80 0.600000000000 1838907 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": 1350970, "vin": [ { "gen": { "height": 1350960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efe6f2f333fee0ade5e4bfd3cc9b1773dcb31194636a5810a6c8905ef148cc80" } } ], "extra": [ 1, 108, 25, 243, 53, 14, 244, 218, 98, 232, 65, 76, 223, 36, 223, 208, 201, 150, 220, 104, 246, 240, 246, 105, 44, 15, 238, 37, 142, 39, 144, 96, 230, 2, 17, 0, 0, 0, 5, 131, 104, 38, 109, 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