← previous blocknext block →recent activity
Analyzing
Block #99,958,733
14 transactions · 13 stateful · 2026-08-28 17:32:31 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,958,733 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w49w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x904bb1d5…0100
0x34b655…2a6f
8 touches
6 conflicts
0x3ac7ef10…579c
0x34b655…2a6f
8 touches
6 conflicts
0x310a7246…2dcb
0x34b655…2a6f
6 touches
3 conflicts
0x9ca6fa7b…aeb3
0x34b655…2a6f
6 touches
3 conflicts
0xd97b0449…00a0
0x34b655…2a6f
4 touches
1 conflict
0x36f63e4f…f319
0x34b655…2a6f
4 touches
1 conflict
0xbfb4b02a…4b47
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
6 conflicts on slot 0x904bb1d5f9…da0100
Audit this contract →
← previous block·next block →recent activity