Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cde6ef50c1598045e3807ef412702f5a2f416d4fc6689e498f1f6179fa093d12

Tx prefix hash: f816c7e1d60781d0994a8db910d09d4b221e246b0c4c2d0eb6aa74ac811c357d
Tx public key: c397502fabc1748491a40985e84ef3308b443c93d0712f27f74c282db9f32b23
Timestamp: 1700994867 Timestamp [UCT]: 2023-11-26 10:34:27 Age [y:d:h:m:s]: 01:131:05:31:19
Block: 899986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354958 RingCT/type: yes/0
Extra: 01c397502fabc1748491a40985e84ef3308b443c93d0712f27f74c282db9f32b23021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.639694716000 dcy

stealth address amount amount idx
00: c3545f1e549999dea2301d3634e39264a984c5bc58bc4ee754845eb8f134b065 0.639694716000 1356459 of 0

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": 899996, "vin": [ { "gen": { "height": 899986 } } ], "vout": [ { "amount": 639694716, "target": { "key": "c3545f1e549999dea2301d3634e39264a984c5bc58bc4ee754845eb8f134b065" } } ], "extra": [ 1, 195, 151, 80, 47, 171, 193, 116, 132, 145, 164, 9, 133, 232, 78, 243, 48, 139, 68, 60, 147, 208, 113, 47, 39, 247, 76, 40, 45, 185, 243, 43, 35, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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