Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 942ae928e70ea86538468dbb2099ab0b625ef7410f7ef2b25882e3971b691dc1

Tx prefix hash: e5458460980b90684a522f13a4917d9a3e95ed48faa3364141dbe97294bd6028
Tx public key: fcdffb2551c81de28065973ae99b5aec77f0a3777d7ad23934a4dc870ca6c454
Timestamp: 1696053161 Timestamp [UCT]: 2023-09-30 05:52:41 Age [y:d:h:m:s]: 01:112:11:05:33
Block: 859228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341611 RingCT/type: yes/0
Extra: 01fcdffb2551c81de28065973ae99b5aec77f0a3777d7ad23934a4dc870ca6c454021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.873013574000 dcy

stealth address amount amount idx
00: 708e97cccc51df07f476ab999446f41c9601b3a16e73a71f2b6f82bab40ac3da 0.873013574000 1313444 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": 859238, "vin": [ { "gen": { "height": 859228 } } ], "vout": [ { "amount": 873013574, "target": { "key": "708e97cccc51df07f476ab999446f41c9601b3a16e73a71f2b6f82bab40ac3da" } } ], "extra": [ 1, 252, 223, 251, 37, 81, 200, 29, 226, 128, 101, 151, 58, 233, 155, 90, 236, 119, 240, 163, 119, 125, 122, 210, 57, 52, 164, 220, 135, 12, 166, 196, 84, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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