Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d767c2cadc2ed992cc9aed5941f9a9a33b7ce0aabc0f0e5919abda91db44c47a

Tx prefix hash: 313d980fd1c94dee327a350d50b03515519e4bcacd285ae5e1cc60889fcc2a18
Tx public key: b0cbc73f82ea20cb5513d5aa6e8ba2f7e3247861404d5baec03bb9948728c48f
Timestamp: 1742506916 Timestamp [UCT]: 2025-03-20 21:41:56 Age [y:d:h:m:s]: 00:052:22:35:29
Block: 1243689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37846 RingCT/type: yes/0
Extra: 01b0cbc73f82ea20cb5513d5aa6e8ba2f7e3247861404d5baec03bb9948728c48f021100000009bfa77623000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08be5ad499220158d4dc12b757b90f493209f59ef416b10569e54353a9622555 0.600000000000 1730676 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": 1243699, "vin": [ { "gen": { "height": 1243689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08be5ad499220158d4dc12b757b90f493209f59ef416b10569e54353a9622555" } } ], "extra": [ 1, 176, 203, 199, 63, 130, 234, 32, 203, 85, 19, 213, 170, 110, 139, 162, 247, 227, 36, 120, 97, 64, 77, 91, 174, 192, 59, 185, 148, 135, 40, 196, 143, 2, 17, 0, 0, 0, 9, 191, 167, 118, 35, 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