← previous blocknext block →recent activity
Analyzing
Block #93,237,782
24 transactions · 20 stateful · 2026-08-05 03:19:14 UTC
Parallelism
67/100
Blocked
55%
Avg conflicts / tx
1.42
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #93,237,782 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w07w18w29w310w311w112w413w514w616w717w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0x05706c2d…4b28
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd8bc53a3…c2fe
0x34b655…2a6f
8 touches
6 conflicts
0x855013b9…62c4
0xd32edf…ff58
7 touches
6 conflicts
0x67a56c8b…f955
0x34b655…2a6f
6 touches
3 conflicts
0x5ecd87b9…32de
0x34b655…2a6f
6 touches
3 conflicts
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity