Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a6cea115099bf0361a11f63f84e0ded67e054d6ef2f47f9c40f9e24fb6da4ca

Tx prefix hash: 9accd4a70115a4d934acc757648f3416c211854c5a2e62d3a5306958e0987734
Tx public key: dd214bc7ddee720f050fafe2fd7f1b5394411256fc7fe6a825ffe03bb8fe9cdf
Timestamp: 1736542886 Timestamp [UCT]: 2025-01-10 21:01:26 Age [y:d:h:m:s]: 00:079:09:55:39
Block: 1194565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56525 RingCT/type: yes/0
Extra: 01dd214bc7ddee720f050fafe2fd7f1b5394411256fc7fe6a825ffe03bb8fe9cdf021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5772b181f04415f9c78acf196a5edf5332f8c0fbade53259b72b74c7b8b7c176 0.600000000000 1681142 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": 1194575, "vin": [ { "gen": { "height": 1194565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5772b181f04415f9c78acf196a5edf5332f8c0fbade53259b72b74c7b8b7c176" } } ], "extra": [ 1, 221, 33, 75, 199, 221, 238, 114, 15, 5, 15, 175, 226, 253, 127, 27, 83, 148, 65, 18, 86, 252, 127, 230, 168, 37, 255, 224, 59, 184, 254, 156, 223, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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