Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 749229c653400635da14d1fd8a95b3882c4d831e233dea6ef833668b6269a0bb

Tx prefix hash: f558918c7a1aa39b7e6aea7f7ccdb33aa3387acc37f07366e97262c5a23c6ba8
Tx public key: 8c531fd1cfaaef2cfd0717ac118c66712b9153e682c5b11790e31bae8bdb4f01
Timestamp: 1717771977 Timestamp [UCT]: 2024-06-07 14:52:57 Age [y:d:h:m:s]: 01:008:19:06:45
Block: 1039094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267068 RingCT/type: yes/0
Extra: 018c531fd1cfaaef2cfd0717ac118c66712b9153e682c5b11790e31bae8bdb4f010211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b09edc89376bd993d5ef4afcf853f7d63f93c348c48b813671651dd1007a42eb 0.600000000000 1507685 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": 1039104, "vin": [ { "gen": { "height": 1039094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b09edc89376bd993d5ef4afcf853f7d63f93c348c48b813671651dd1007a42eb" } } ], "extra": [ 1, 140, 83, 31, 209, 207, 170, 239, 44, 253, 7, 23, 172, 17, 140, 102, 113, 43, 145, 83, 230, 130, 197, 177, 23, 144, 227, 27, 174, 139, 219, 79, 1, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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