Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69797a3e4d854df4464cdf4d5069159231a032b8f5887b6ad94683868e4407be

Tx prefix hash: 28c25b869092ccfde46d41ba038b71fb593decde6cb16694a6dc14f442c3f32e
Tx public key: d3f33db89ef4a5a5411a6e14acb04c33e33d4580462a65914479c401d4cb3067
Timestamp: 1761679392 Timestamp [UCT]: 2025-10-28 19:23:12 Age [y:d:h:m:s]: 00:011:10:16:23
Block: 1399987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8173 RingCT/type: yes/0
Extra: 01d3f33db89ef4a5a5411a6e14acb04c33e33d4580462a65914479c401d4cb306702110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c932edeea00bae002176aae36bf6ad6bdce4c23b5e09a3ef8b450fcd23f3aac6 0.600000000000 1888294 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": 1399997, "vin": [ { "gen": { "height": 1399987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c932edeea00bae002176aae36bf6ad6bdce4c23b5e09a3ef8b450fcd23f3aac6" } } ], "extra": [ 1, 211, 243, 61, 184, 158, 244, 165, 165, 65, 26, 110, 20, 172, 176, 76, 51, 227, 61, 69, 128, 70, 42, 101, 145, 68, 121, 196, 1, 212, 203, 48, 103, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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