Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9be6aafd6b49feb2cf4c2145da9ae370b4ad71c789e62ec9f6ab3224655630b2

Tx prefix hash: 7d395b633412e0a476922b354896c929a561937ed6f47c2afb786f07f7202ba7
Tx public key: e9882f435f77b7d6c82541b428863bf8e2c17d109e590e50df38312992a5fad6
Timestamp: 1677142903 Timestamp [UCT]: 2023-02-23 09:01:43 Age [y:d:h:m:s]: 02:112:10:45:20
Block: 703133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 601910 RingCT/type: yes/0
Extra: 01e9882f435f77b7d6c82541b428863bf8e2c17d109e590e50df38312992a5fad602110000000174b6d784000000000000000000

1 output(s) for total of 2.872290721000 dcy

stealth address amount amount idx
00: 8099497f9745c6d84759a3c55612ce5945bf66345d01c8b573f9a359eab7fdc4 2.872290721000 1146690 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": 703143, "vin": [ { "gen": { "height": 703133 } } ], "vout": [ { "amount": 2872290721, "target": { "key": "8099497f9745c6d84759a3c55612ce5945bf66345d01c8b573f9a359eab7fdc4" } } ], "extra": [ 1, 233, 136, 47, 67, 95, 119, 183, 214, 200, 37, 65, 180, 40, 134, 59, 248, 226, 193, 125, 16, 158, 89, 14, 80, 223, 56, 49, 41, 146, 165, 250, 214, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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