← previous blocknext block →recent activity
Analyzing
Block #109,237,903
30 transactions · 24 stateful · 2026-09-30 05:24:47 UTC
Parallelism
80/100
Blocked
46%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #109,237,903 · 30 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
2w05w06w18w19w214w015w116w217w318w419w520w521w128w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb8313d5c…8ef5
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x18e86f02…fa98
0x34b655…2a6f
4 touches
1 conflict
0x35a6cb81…46d2
0x34b655…2a6f
4 touches
1 conflict
0x396f6e9a…f9c5
0x34b655…2a6f
4 touches
1 conflict
0x43c932f1…f80f
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
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 0xb8313d5c48…658ef5
Audit this contract →
← previous block·next block →recent activity