Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 611d067650590743eed72873780e2430a701d14d259728a640843160bcca752c

Tx prefix hash: b279f25b5427c5915b3ac35702373cbe04849c1542d00cd9e361b5bb13d9b6ea
Tx public key: e4a63630a39032a52df2db0aeab29a5061504a039c7b3dc7f0585c1a78ef13fa
Timestamp: 1760129869 Timestamp [UCT]: 2025-10-10 20:57:49 Age [y:d:h:m:s]: 00:033:16:45:28
Block: 1387140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24123 RingCT/type: yes/0
Extra: 01e4a63630a39032a52df2db0aeab29a5061504a039c7b3dc7f0585c1a78ef13fa02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b62a13a4f9d90d75d6d4eb94a1da4519dd2f5c62f5366685ea08ad3a59b03c9 0.600000000000 1875327 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": 1387150, "vin": [ { "gen": { "height": 1387140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b62a13a4f9d90d75d6d4eb94a1da4519dd2f5c62f5366685ea08ad3a59b03c9" } } ], "extra": [ 1, 228, 166, 54, 48, 163, 144, 50, 165, 45, 242, 219, 10, 234, 178, 154, 80, 97, 80, 74, 3, 156, 123, 61, 199, 240, 88, 92, 26, 120, 239, 19, 250, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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