Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f28910459f7f4be8338ef72f0d8551f8b4079bde059648e1f1381f6fc0d2f035

Tx prefix hash: d66625fc345678fe36f8cd311ad3ce9753a700a46785c6d1d24d4eb3a7205e82
Tx public key: a0ac2a3aedc83fa9c4934c93defa3677fd511586961a5fd6add3b99e4e09d855
Timestamp: 1721887670 Timestamp [UCT]: 2024-07-25 06:07:50 Age [y:d:h:m:s]: 00:258:18:44:42
Block: 1073196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184870 RingCT/type: yes/0
Extra: 01a0ac2a3aedc83fa9c4934c93defa3677fd511586961a5fd6add3b99e4e09d85502110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 254f3abc0a9904260da4109e2393ffebdabb49119246bdc3c40e5b2b6f2198f4 0.600000000000 1545695 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": 1073206, "vin": [ { "gen": { "height": 1073196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "254f3abc0a9904260da4109e2393ffebdabb49119246bdc3c40e5b2b6f2198f4" } } ], "extra": [ 1, 160, 172, 42, 58, 237, 200, 63, 169, 196, 147, 76, 147, 222, 250, 54, 119, 253, 81, 21, 134, 150, 26, 95, 214, 173, 211, 185, 158, 78, 9, 216, 85, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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