Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ab793e07f710f48c11b85ad9776560fe5d377bc5af1c362bd088c845fa44a0d

Tx prefix hash: 811c514542891e79e76e027a19843be38374a157c8b5574c5f00657c03c16e38
Tx public key: 25e4bcfa12ad573463a105b95fba13eb599a6736dbc8f052e934e0c4ed4e8e7b
Timestamp: 1717128513 Timestamp [UCT]: 2024-05-31 04:08:33 Age [y:d:h:m:s]: 01:164:04:02:18
Block: 1033754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375911 RingCT/type: yes/0
Extra: 0125e4bcfa12ad573463a105b95fba13eb599a6736dbc8f052e934e0c4ed4e8e7b02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf11ff8265a3666494a1bd581ce5d4e42c103a0b43953c9fdd7adccc03a432b8 0.600000000000 1502225 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": 1033764, "vin": [ { "gen": { "height": 1033754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf11ff8265a3666494a1bd581ce5d4e42c103a0b43953c9fdd7adccc03a432b8" } } ], "extra": [ 1, 37, 228, 188, 250, 18, 173, 87, 52, 99, 161, 5, 185, 95, 186, 19, 235, 89, 154, 103, 54, 219, 200, 240, 82, 233, 52, 224, 196, 237, 78, 142, 123, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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