Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d113c39081aac3fe42367f8b0d16f4405a372bca807b5bced99088a58c4b5e0c

Tx prefix hash: 2faf3141be7c8422158369f1e10e001cc34b3053c7e86661e848ccc3caf6d73f
Tx public key: 3810d126d49394e2dc33341ca9dcb44b34c9900e1fe3aac8c22210f3f7ac268c
Timestamp: 1720596100 Timestamp [UCT]: 2024-07-10 07:21:40 Age [y:d:h:m:s]: 00:310:18:48:10
Block: 1062509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222065 RingCT/type: yes/0
Extra: 013810d126d49394e2dc33341ca9dcb44b34c9900e1fe3aac8c22210f3f7ac268c02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04f4704f417441e30973b78381b058fd97af64a9f10e73b493f5900ce9409581 0.600000000000 1533012 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": 1062519, "vin": [ { "gen": { "height": 1062509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04f4704f417441e30973b78381b058fd97af64a9f10e73b493f5900ce9409581" } } ], "extra": [ 1, 56, 16, 209, 38, 212, 147, 148, 226, 220, 51, 52, 28, 169, 220, 180, 75, 52, 201, 144, 14, 31, 227, 170, 200, 194, 34, 16, 243, 247, 172, 38, 140, 2, 17, 0, 0, 0, 7, 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