← previous blocknext block →recent activity
Analyzing
Block #109,236,255
18 transactions · 16 stateful · 2026-09-30 05:16:30 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #109,236,255 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w17w28w39w410w014w516w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3503e240…797a
0x34b655…2a6f
10 touches
10 conflicts
0xf346808d…6ad4
0x34b655…2a6f
8 touches
6 conflicts
0xd547ecab…22a3
0x34b655…2a6f
8 touches
6 conflicts
0xebe581d8…2696
0x34b655…2a6f
6 touches
3 conflicts
0xe2f43374…2b02
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x336486a4…20bd
0x34b655…2a6f
4 touches
1 conflict
0x6ca0994e…02ef
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
10 conflicts on slot 0x3503e240ad…63797a
Audit this contract →
← previous block·next block →recent activity