Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bcb140d068aec1dc2f7ad274de4ef8ebd3d09161944367f66aaf8159f8bcffc

Tx prefix hash: d19160afc64a320bff70cf0b9f0b601c7b720ac583c2e8e9a2c54259780f2978
Tx public key: a6f6e49e5f41bb825930c69c8507ecef3f82521e9e998226090f51dd2f8bb65a
Timestamp: 1738145145 Timestamp [UCT]: 2025-01-29 10:05:45 Age [y:d:h:m:s]: 00:143:18:10:57
Block: 1207570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102641 RingCT/type: yes/0
Extra: 01a6f6e49e5f41bb825930c69c8507ecef3f82521e9e998226090f51dd2f8bb65a0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 141d62040adff52af9f9305948c95ea11e4c812767e107fb3286d10c4ef1644a 0.600000000000 1694295 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": 1207580, "vin": [ { "gen": { "height": 1207570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "141d62040adff52af9f9305948c95ea11e4c812767e107fb3286d10c4ef1644a" } } ], "extra": [ 1, 166, 246, 228, 158, 95, 65, 187, 130, 89, 48, 198, 156, 133, 7, 236, 239, 63, 130, 82, 30, 158, 153, 130, 38, 9, 15, 81, 221, 47, 139, 182, 90, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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