← previous blocknext block →recent activity
Analyzing
Block #93,594,962
19 transactions · 17 stateful · 2026-08-06 09:14:57 UTC
Parallelism
63/100
Blocked
35%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,594,962 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w27w38w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x595de029…7d05
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x8743e1ba…8331
0x34b655…2a6f
6 touches
3 conflicts
0xe4af4c87…9964
0x34b655…2a6f
6 touches
3 conflicts
0x310afe2c…83e1
0x34b655…2a6f
6 touches
3 conflicts
0x6719a767…9d62
0x34b655…2a6f
4 touches
1 conflict
0x0ec7fb56…bca1
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
21 conflicts on slot 0x595de0299f…ab7d05
Audit this contract →
← previous block·next block →recent activity