Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 837c0a9ed48aa2416de59c2e3c91dca0f52351a72b49b57dfc4e066d82e94577

Tx prefix hash: 5196469b298ef80a969696a68a068b0945afcca166e5f8f22cf30a686ac43b3d
Tx public key: db1f09fa116b9660f316c3a8d1a98cc51126d878fed40f9f61095f4a1271ce1f
Timestamp: 1760685236 Timestamp [UCT]: 2025-10-17 07:13:56 Age [y:d:h:m:s]: 00:067:17:03:25
Block: 1391747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48461 RingCT/type: yes/0
Extra: 01db1f09fa116b9660f316c3a8d1a98cc51126d878fed40f9f61095f4a1271ce1f0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ccbed5a8f1e3a1eac19eba99fcb2f28ad9e3cc44c71586ad7f5584b1b48309b 0.600000000000 1879994 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": 1391757, "vin": [ { "gen": { "height": 1391747 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ccbed5a8f1e3a1eac19eba99fcb2f28ad9e3cc44c71586ad7f5584b1b48309b" } } ], "extra": [ 1, 219, 31, 9, 250, 17, 107, 150, 96, 243, 22, 195, 168, 209, 169, 140, 197, 17, 38, 216, 120, 254, 212, 15, 159, 97, 9, 95, 74, 18, 113, 206, 31, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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