Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93ee01d4737e686e0edcc8455cc184deaba79fb1f69a2f04e1815663cac095d8

Tx prefix hash: c2c3d053d844c96388b38459a900b5ec73c4f1967c58db7b0db8b2998b8ad4f9
Tx public key: edfff9675bf5b3fa6bcb2a4cc5a527db0bb6d5bf859369d51c5dd1e85691bd96
Timestamp: 1703665013 Timestamp [UCT]: 2023-12-27 08:16:53 Age [y:d:h:m:s]: 01:096:06:00:15
Block: 922132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329892 RingCT/type: yes/0
Extra: 01edfff9675bf5b3fa6bcb2a4cc5a527db0bb6d5bf859369d51c5dd1e85691bd9602110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf6b24d371e344683193cf5f8836a0a88ede29b74d8ae3c07a8b1950845bf169 0.600000000000 1379826 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": 922142, "vin": [ { "gen": { "height": 922132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf6b24d371e344683193cf5f8836a0a88ede29b74d8ae3c07a8b1950845bf169" } } ], "extra": [ 1, 237, 255, 249, 103, 91, 245, 179, 250, 107, 203, 42, 76, 197, 165, 39, 219, 11, 182, 213, 191, 133, 147, 105, 213, 28, 93, 209, 232, 86, 145, 189, 150, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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