← previous blocknext block →recent activity
Analyzing
Block #93,239,310
12 transactions · 11 stateful · 2026-08-05 03:26:55 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,239,310 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c5fe4bc…a768
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x1655cc1a…31e7
0x34b655…2a6f
2 touches
0 conflicts
0x176afbb9…78da
0x34b655…2a6f
2 touches
0 conflicts
0x2434a4e3…9e52
0x34b655…2a6f
2 touches
0 conflicts
0x33afbaa4…b28d
0x34b655…2a6f
2 touches
0 conflicts
0x764f042f…f8b8
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x3c5fe4bcf9…c1a768
Audit this contract →
← previous block·next block →recent activity