Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dc52d42c8b647cb0b91b0130d9a7a8e231adae1eea70899fd5857b2206a2bb1

Tx prefix hash: 1260432df86e3ef8d32483d35b616a641856486205aca65a9a3f12e5f34ef7ff
Tx public key: 7c002494ff04d43cad542f5b3f09e45eecd9db6aacfd8fffacea34652fb8d5fb
Timestamp: 1738393090 Timestamp [UCT]: 2025-02-01 06:58:10 Age [y:d:h:m:s]: 00:362:09:39:01
Block: 1209611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256693 RingCT/type: yes/0
Extra: 017c002494ff04d43cad542f5b3f09e45eecd9db6aacfd8fffacea34652fb8d5fb0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf8e965225e68357ca69ea301ee5a24e4aec688f5567a0b5a162005d3038dd09 0.600000000000 1696356 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": 1209621, "vin": [ { "gen": { "height": 1209611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf8e965225e68357ca69ea301ee5a24e4aec688f5567a0b5a162005d3038dd09" } } ], "extra": [ 1, 124, 0, 36, 148, 255, 4, 212, 60, 173, 84, 47, 91, 63, 9, 228, 94, 236, 217, 219, 106, 172, 253, 143, 255, 172, 234, 52, 101, 47, 184, 213, 251, 2, 17, 0, 0, 0, 3, 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