Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6098bdccfbb7728c2c8a7cefa81327e4a80ed88f712ee3fc24b54dc750d93822

Tx prefix hash: 70dc004ed222e5ae1cb8e6ff7200c50efcebeda1f6e25df2216de02919be5579
Tx public key: 7f5011a1bd5f588801054fedfdb5c24247dcbe79ab4922dda2a291b1b049e44b
Timestamp: 1727514283 Timestamp [UCT]: 2024-09-28 09:04:43 Age [y:d:h:m:s]: 00:190:17:51:36
Block: 1119859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136107 RingCT/type: yes/0
Extra: 017f5011a1bd5f588801054fedfdb5c24247dcbe79ab4922dda2a291b1b049e44b021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54c4e6033b136fb09104b4e7bffbe3c95dc411502c8898f2a5cc184aca25f4c6 0.600000000000 1601570 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": 1119869, "vin": [ { "gen": { "height": 1119859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54c4e6033b136fb09104b4e7bffbe3c95dc411502c8898f2a5cc184aca25f4c6" } } ], "extra": [ 1, 127, 80, 17, 161, 189, 95, 88, 136, 1, 5, 79, 237, 253, 181, 194, 66, 71, 220, 190, 121, 171, 73, 34, 221, 162, 162, 145, 177, 176, 73, 228, 75, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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