← previous blocknext block →recent activity
Analyzing
Block #109,056,836
19 transactions · 18 stateful · 2026-09-29 14:12:34 UTC
Parallelism
84/100
Blocked
28%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #109,056,836 · 19 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
1w02w16w07w18w09w115w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d9ef283…ddd1
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x46c14e01…ff09
0x34b655…2a6f
4 touches
1 conflict
0xde3776fd…dd9e
0xd32edf…ff58
3 touches
1 conflict
0x1972739d…a40b
0x34b655…2a6f
2 touches
0 conflicts
0x3eb53cbf…2df7
0x34b655…2a6f
2 touches
0 conflicts
0x5ad5e6de…e7ad
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 0x7d9ef2836a…01ddd1
Audit this contract →
← previous block·next block →recent activity