Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a06913d709a842f074ad32325edaf84d59cf4b61d2c9075d76b2cc6b384d73d

Tx prefix hash: c705cf35d48fd905145be9d48290dcdc2825fbab2fb7bbb6a59d9a1f38f7be07
Tx public key: 9cf2522f4e54e471dd5def78af9c5e7fa66bcbbacd558da8645c3d53e8f83ac1
Timestamp: 1665958921 Timestamp [UCT]: 2022-10-16 22:22:01 Age [y:d:h:m:s]: 02:098:17:36:22
Block: 610570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 592380 RingCT/type: yes/0
Extra: 019cf2522f4e54e471dd5def78af9c5e7fa66bcbbacd558da8645c3d53e8f83ac102110000000775e3f0e9000000000000000000

1 output(s) for total of 5.820069552000 dcy

stealth address amount amount idx
00: eb97612989c6d1b6749227f5d37ecc0a751133964d42f9a47ef80e04e7662139 5.820069552000 1047570 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": 610580, "vin": [ { "gen": { "height": 610570 } } ], "vout": [ { "amount": 5820069552, "target": { "key": "eb97612989c6d1b6749227f5d37ecc0a751133964d42f9a47ef80e04e7662139" } } ], "extra": [ 1, 156, 242, 82, 47, 78, 84, 228, 113, 221, 93, 239, 120, 175, 156, 94, 127, 166, 107, 203, 186, 205, 85, 141, 168, 100, 92, 61, 83, 232, 248, 58, 193, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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