Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cb3b2af4883c22e808977d7120f0f0b1d8a3e1da5becebc1dcdb0d7bffbdf3a

Tx prefix hash: be5144bb975d41911ecef6ae34feda9abebb8041086cd94eb4b204edd6ad767b
Tx public key: 0b54157ab25991d696d0691c8908a87a3aadadbff178601c98c45a056b3a09a2
Timestamp: 1758056665 Timestamp [UCT]: 2025-09-16 21:04:25 Age [y:d:h:m:s]: 00:058:23:35:58
Block: 1369949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42245 RingCT/type: yes/0
Extra: 010b54157ab25991d696d0691c8908a87a3aadadbff178601c98c45a056b3a09a2021100000001ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f60728c104216fbc2dd2566cd0c928c8daf3f4c6f36d32fd82aea277dadf94e5 0.600000000000 1858024 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": 1369959, "vin": [ { "gen": { "height": 1369949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f60728c104216fbc2dd2566cd0c928c8daf3f4c6f36d32fd82aea277dadf94e5" } } ], "extra": [ 1, 11, 84, 21, 122, 178, 89, 145, 214, 150, 208, 105, 28, 137, 8, 168, 122, 58, 173, 173, 191, 241, 120, 96, 28, 152, 196, 90, 5, 107, 58, 9, 162, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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