Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd03576f68bbbddc78e2260659493a5d0953a6a72a6e6955b279633f398846f3

Tx prefix hash: 9238ae7942445add8e80b1c6502ff2bd50d23c62ec0d967277dcaa0195b5b0c0
Tx public key: 0a935e17e01935fee96c4b765cf0794e59a7eaef33ba0345cceb7e38eddfa4fe
Timestamp: 1752518283 Timestamp [UCT]: 2025-07-14 18:38:03 Age [y:d:h:m:s]: 00:176:20:20:50
Block: 1325495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125196 RingCT/type: yes/0
Extra: 010a935e17e01935fee96c4b765cf0794e59a7eaef33ba0345cceb7e38eddfa4fe021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a5f3a1650e01a0e23f83e0fb5c3272d498cee0d0531299cd04a230a17905764 0.600000000000 1813240 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": 1325505, "vin": [ { "gen": { "height": 1325495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a5f3a1650e01a0e23f83e0fb5c3272d498cee0d0531299cd04a230a17905764" } } ], "extra": [ 1, 10, 147, 94, 23, 224, 25, 53, 254, 233, 108, 75, 118, 92, 240, 121, 78, 89, 167, 234, 239, 51, 186, 3, 69, 204, 235, 126, 56, 237, 223, 164, 254, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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