Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35e5a080fa7ad3dc47348d3eac8181ed01a83703074879c1f0a26d3ed6fcca32

Tx prefix hash: 507f151a7f78f54cdf3e383f1bb26b0a39ec8b2ce2d850afbfb4cb29562d50a1
Tx public key: 3068691212751591d44ef4c111664124b87a4524d3adcb934c1e0b96da8a43d9
Timestamp: 1724529643 Timestamp [UCT]: 2024-08-24 20:00:43 Age [y:d:h:m:s]: 00:272:07:56:27
Block: 1095135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194516 RingCT/type: yes/0
Extra: 013068691212751591d44ef4c111664124b87a4524d3adcb934c1e0b96da8a43d9021100000002e337358e000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50f422f541b244ea3a411072962fd95dc089d925ccea2e81a76f81e18704420c 0.600000000000 1570280 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": 1095145, "vin": [ { "gen": { "height": 1095135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50f422f541b244ea3a411072962fd95dc089d925ccea2e81a76f81e18704420c" } } ], "extra": [ 1, 48, 104, 105, 18, 18, 117, 21, 145, 212, 78, 244, 193, 17, 102, 65, 36, 184, 122, 69, 36, 211, 173, 203, 147, 76, 30, 11, 150, 218, 138, 67, 217, 2, 17, 0, 0, 0, 2, 227, 55, 53, 142, 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