Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1acc322af857134b460ec0daef14fb98c9fb4f7bbe4d51a8a5cc6591352ac65b

Tx prefix hash: 99b641b6d5220513eabc3702f95be99c942cbd69cb41ee04c674be4016d54578
Tx public key: e974c4a8386242bf1e0c4f62fd5155a440ee91d9f712debd6e8c27af0c34c219
Timestamp: 1743596570 Timestamp [UCT]: 2025-04-02 12:22:50 Age [y:d:h:m:s]: 00:230:05:27:39
Block: 1252695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162277 RingCT/type: yes/0
Extra: 01e974c4a8386242bf1e0c4f62fd5155a440ee91d9f712debd6e8c27af0c34c219021100000010a2ed016b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 891f238bca32b99090d520e4827b777fc6426d9c54df0054019beea56806c671 0.600000000000 1739776 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": 1252705, "vin": [ { "gen": { "height": 1252695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "891f238bca32b99090d520e4827b777fc6426d9c54df0054019beea56806c671" } } ], "extra": [ 1, 233, 116, 196, 168, 56, 98, 66, 191, 30, 12, 79, 98, 253, 81, 85, 164, 64, 238, 145, 217, 247, 18, 222, 189, 110, 140, 39, 175, 12, 52, 194, 25, 2, 17, 0, 0, 0, 16, 162, 237, 1, 107, 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