← previous blocknext block →recent activity
Analyzing
Block #109,133,888
7 transactions · 6 stateful · 2026-09-29 20:40:53 UTC
Parallelism
57/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #109,133,888 · 7 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc853be2d…b18f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xe48c5086…c9b7
0x000000…012a
2 touches
0 conflicts
0xe7fa6db5…a6d4
0x000000…012a
2 touches
0 conflicts
0xada50131…9e7d
0x261b4f…cb78
2 touches
0 conflicts
0x0139015c…4aa2
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 0xc853be2d22…5eb18f
Audit this contract →
← previous block·next block →recent activity