Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3acbab85b424dd82dd1410dcb97dc535ef47c626aeb110c48ae376af497ca47f

Tx prefix hash: 466f0e9bdaf35efce964c33a285e41d0dbb12e5327ba32cf7a9c6ccb29e3816b
Tx public key: 415c2c0840dcd94a47127bd33a9fa1e51cb672507d7fef8f0df2634678c7d18b
Timestamp: 1737303486 Timestamp [UCT]: 2025-01-19 16:18:06 Age [y:d:h:m:s]: 00:149:23:47:18
Block: 1200825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106936 RingCT/type: yes/0
Extra: 01415c2c0840dcd94a47127bd33a9fa1e51cb672507d7fef8f0df2634678c7d18b02110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ffcf1c4f1000840ecc4b3cc46624cf855c4fa7a0850ac74acdeeb7cf3f3b875 0.600000000000 1687472 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": 1200835, "vin": [ { "gen": { "height": 1200825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ffcf1c4f1000840ecc4b3cc46624cf855c4fa7a0850ac74acdeeb7cf3f3b875" } } ], "extra": [ 1, 65, 92, 44, 8, 64, 220, 217, 74, 71, 18, 123, 211, 58, 159, 161, 229, 28, 182, 114, 80, 125, 127, 239, 143, 13, 242, 99, 70, 120, 199, 209, 139, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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