Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f1ddf851852b1fb74d93d260d6eae1023781b8c5994c2541ffcaf0909ce959c

Tx prefix hash: 8cd2609a953b05770071dd13c54d5dc0018d9c21495852977d48d0f92bee2a7f
Tx public key: 96938ef7c58cbbe59e5da8ee57b86d39323b9ee16d75a806c291c6717836b9f7
Timestamp: 1732554946 Timestamp [UCT]: 2024-11-25 17:15:46 Age [y:d:h:m:s]: 00:135:03:06:17
Block: 1161543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96381 RingCT/type: yes/0
Extra: 0196938ef7c58cbbe59e5da8ee57b86d39323b9ee16d75a806c291c6717836b9f7021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b3bde5c17d3a009a7275636c788ccc250660c82b4ae7bad3377718c2a42befa 0.600000000000 1647198 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": 1161553, "vin": [ { "gen": { "height": 1161543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b3bde5c17d3a009a7275636c788ccc250660c82b4ae7bad3377718c2a42befa" } } ], "extra": [ 1, 150, 147, 142, 247, 197, 140, 187, 229, 158, 93, 168, 238, 87, 184, 109, 57, 50, 59, 158, 225, 109, 117, 168, 6, 194, 145, 198, 113, 120, 54, 185, 247, 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