Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c4b4cdc870e86b3ea12d073409330013afdb042096a576b203c5a3d2e7267fd

Tx prefix hash: e82bb923c121f9d33ad94683fbeb6afdf5803ed271b69144c248cfdd93ebec7d
Tx public key: d43dfd817b7426b730515f28d52d364075b0f251afcf5ff63d4f52b46bd2bd90
Timestamp: 1714100754 Timestamp [UCT]: 2024-04-26 03:05:54 Age [y:d:h:m:s]: 00:304:23:01:44
Block: 1008636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217976 RingCT/type: yes/0
Extra: 01d43dfd817b7426b730515f28d52d364075b0f251afcf5ff63d4f52b46bd2bd9002110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2c3422d129499017d87c70062569ea2b596dd46f01c62bbf271ce7a45de48fb 0.600000000000 1470108 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": 1008646, "vin": [ { "gen": { "height": 1008636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2c3422d129499017d87c70062569ea2b596dd46f01c62bbf271ce7a45de48fb" } } ], "extra": [ 1, 212, 61, 253, 129, 123, 116, 38, 183, 48, 81, 95, 40, 213, 45, 54, 64, 117, 176, 242, 81, 175, 207, 95, 246, 61, 79, 82, 180, 107, 210, 189, 144, 2, 17, 0, 0, 0, 4, 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