Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a1e369010a68f765367e92e2bee80b2a84bf511dd70e10ca6bac027f1e1a34d

Tx prefix hash: 33b99802d9d59aa732eafc4c6441cf72a7daf50cad6658c958371c013750cf1a
Tx public key: c04ea5f2f88b3b590950cc57de0f9d56ae56608fe4278733ad01ba1b9869a434
Timestamp: 1706977449 Timestamp [UCT]: 2024-02-03 16:24:09 Age [y:d:h:m:s]: 01:061:15:48:05
Block: 949573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305143 RingCT/type: yes/0
Extra: 01c04ea5f2f88b3b590950cc57de0f9d56ae56608fe4278733ad01ba1b9869a4340211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f952644f1bce098f3ea9c2d8fad76aa96f63010acf66539b3b92d8bfa8b91a6b 0.600000000000 1408103 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": 949583, "vin": [ { "gen": { "height": 949573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f952644f1bce098f3ea9c2d8fad76aa96f63010acf66539b3b92d8bfa8b91a6b" } } ], "extra": [ 1, 192, 78, 165, 242, 248, 139, 59, 89, 9, 80, 204, 87, 222, 15, 157, 86, 174, 86, 96, 143, 228, 39, 135, 51, 173, 1, 186, 27, 152, 105, 164, 52, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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