Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cb6c8241bd5f23b561be1170cbdfca64657b17679f1be7a5bb38e38536392c3

Tx prefix hash: f94de9e590df2d373d684e13f25235a1761c82a6dc6ac1bd66ac517edbab188f
Tx public key: 6816fac99bcc6c7f1c9fdb54d6572307d7b99707d9445fd7e800dff49a87e79a
Timestamp: 1710165468 Timestamp [UCT]: 2024-03-11 13:57:48 Age [y:d:h:m:s]: 01:014:20:20:06
Block: 976033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271577 RingCT/type: yes/0
Extra: 016816fac99bcc6c7f1c9fdb54d6572307d7b99707d9445fd7e800dff49a87e79a0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3066545f4d82a72aae4ba9425f1c22b133a5e2d8cdefd5c3c6762bd9fb660810 0.600000000000 1436016 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": 976043, "vin": [ { "gen": { "height": 976033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3066545f4d82a72aae4ba9425f1c22b133a5e2d8cdefd5c3c6762bd9fb660810" } } ], "extra": [ 1, 104, 22, 250, 201, 155, 204, 108, 127, 28, 159, 219, 84, 214, 87, 35, 7, 215, 185, 151, 7, 217, 68, 95, 215, 232, 0, 223, 244, 154, 135, 231, 154, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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