Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14b5931f251066acbdf44856319dfeab59855f3c322b53e97b4c56cb5c70d6b9

Tx prefix hash: 9d7f84e5f0982836592e587f613a8e5fd1195666f41e87254cc8e62cb9881cf3
Tx public key: da5dc487338f2fbc6d0b08676c5049c622729be47af5c7792114aee8930daff6
Timestamp: 1710711204 Timestamp [UCT]: 2024-03-17 21:33:24 Age [y:d:h:m:s]: 01:005:12:15:07
Block: 980566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264900 RingCT/type: yes/0
Extra: 01da5dc487338f2fbc6d0b08676c5049c622729be47af5c7792114aee8930daff602110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1110a026a68f0bcfffe7b5c78239d3fae737e7a6d7bec15ad2f33b4ab626cf07 0.600000000000 1440641 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": 980576, "vin": [ { "gen": { "height": 980566 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1110a026a68f0bcfffe7b5c78239d3fae737e7a6d7bec15ad2f33b4ab626cf07" } } ], "extra": [ 1, 218, 93, 196, 135, 51, 143, 47, 188, 109, 11, 8, 103, 108, 80, 73, 198, 34, 114, 155, 228, 122, 245, 199, 121, 33, 20, 174, 232, 147, 13, 175, 246, 2, 17, 0, 0, 0, 12, 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