Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e06b6358f37e74bec2fe24794c28a3561a38980753779f46f799614c2de4580e

Tx prefix hash: eee59b4e7e9ea9107c7238ed2946aa04810f31180a514dd96b5e64602c90d1bf
Tx public key: cf352a2bcb95b5f52dd8b4d4f4801f97070b87680b77fbc307c5cc79f203b73c
Timestamp: 1672300530 Timestamp [UCT]: 2022-12-29 07:55:30 Age [y:d:h:m:s]: 02:315:02:59:27
Block: 662956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 744640 RingCT/type: yes/0
Extra: 01cf352a2bcb95b5f52dd8b4d4f4801f97070b87680b77fbc307c5cc79f203b73c021100000003e7ace25d000000000000000000

1 output(s) for total of 3.902577474000 dcy

stealth address amount amount idx
00: 05a036a23c5e24c8fa3e839cb72d9e0dde7fd8bd033b862428f803df8921a8cb 3.902577474000 1103829 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": 662966, "vin": [ { "gen": { "height": 662956 } } ], "vout": [ { "amount": 3902577474, "target": { "key": "05a036a23c5e24c8fa3e839cb72d9e0dde7fd8bd033b862428f803df8921a8cb" } } ], "extra": [ 1, 207, 53, 42, 43, 203, 149, 181, 245, 45, 216, 180, 212, 244, 128, 31, 151, 7, 11, 135, 104, 11, 119, 251, 195, 7, 197, 204, 121, 242, 3, 183, 60, 2, 17, 0, 0, 0, 3, 231, 172, 226, 93, 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