← previous blocknext block →recent activity
Analyzing
Block #93,921,935
20 transactions · 17 stateful · 2026-08-07 12:39:12 UTC
Parallelism
80/100
Blocked
59%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,921,935 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w06w17w19w110w311w012w213w214w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41377979…0a18
0x34b655…2a6f
6 touches
3 conflicts
0xf7640726…19a2
0x2a68ba…90c5
4 touches
1 conflict
0x0f6b75e6…34b0
0x34b655…2a6f
4 touches
1 conflict
0x146eca10…e08b
0x34b655…2a6f
4 touches
1 conflict
0x1903eb8c…d126
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
3 conflicts on slot 0x413779793d…8f0a18
Audit this contract →
← previous block·next block →recent activity