Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5041fcc285915e30b0d71f064feae5b47e91f409d676557a157849f93b1dd744

Tx prefix hash: 1daedbd37d80090e58f9a9d5c6e7796c8ecbf5f378f0638b5bb54cd910d958ea
Tx public key: acf853da4f56a47ffd22d2e664c21a7c0d41d530d73cbbbd12110d4606b49aec
Timestamp: 1734274459 Timestamp [UCT]: 2024-12-15 14:54:19 Age [y:d:h:m:s]: 00:132:10:50:14
Block: 1175809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94447 RingCT/type: yes/0
Extra: 01acf853da4f56a47ffd22d2e664c21a7c0d41d530d73cbbbd12110d4606b49aec0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77494d08f991ef9773c0cd6552ab6c507e167803745a3a97294019c3be656b6e 0.600000000000 1662134 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": 1175819, "vin": [ { "gen": { "height": 1175809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77494d08f991ef9773c0cd6552ab6c507e167803745a3a97294019c3be656b6e" } } ], "extra": [ 1, 172, 248, 83, 218, 79, 86, 164, 127, 253, 34, 210, 230, 100, 194, 26, 124, 13, 65, 213, 48, 215, 60, 187, 189, 18, 17, 13, 70, 6, 180, 154, 236, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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