Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa699164f2bd911dd6fbbd5e66186e2882ef407504f249120a6da55d8bcaf879

Tx prefix hash: 1a6fafdac4762b7994e317c79df96791d09633c0a864018f0a7f3abeae40822d
Tx public key: dcb0b603f838dcc5a3125f7c2918b8e77df89e1928a3b7256051681d89676940
Timestamp: 1723119558 Timestamp [UCT]: 2024-08-08 12:19:18 Age [y:d:h:m:s]: 00:076:11:01:38
Block: 1083417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54738 RingCT/type: yes/0
Extra: 01dcb0b603f838dcc5a3125f7c2918b8e77df89e1928a3b7256051681d8967694002110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49a522a7f3deece50a36f4d146ffe535bb5059545ed4523e797e2add9f132d90 0.600000000000 1557328 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": 1083427, "vin": [ { "gen": { "height": 1083417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49a522a7f3deece50a36f4d146ffe535bb5059545ed4523e797e2add9f132d90" } } ], "extra": [ 1, 220, 176, 182, 3, 248, 56, 220, 197, 163, 18, 95, 124, 41, 24, 184, 231, 125, 248, 158, 25, 40, 163, 183, 37, 96, 81, 104, 29, 137, 103, 105, 64, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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