← previous blocknext block →recent activity
Analyzing
Block #109,229,203
19 transactions · 16 stateful · 2026-09-30 04:41:00 UTC
Parallelism
74/100
Blocked
44%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,229,203 · 19 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
1w04w15w06w17w28w39w411w415w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x426126a4…740b
0x34b655…2a6f
8 touches
6 conflicts
0x7d9ef283…ddd1
0x34b655…2a6f
6 touches
3 conflicts
0x740943d3…ef43
0x34b655…2a6f
6 touches
3 conflicts
0x4073f47e…39e6
0x34b655…2a6f
4 touches
1 conflict
0xf6deafb5…5c25
0x34b655…2a6f
4 touches
1 conflict
0x23769ebc…c8ed
0x34b655…2a6f
4 touches
1 conflict
0x4073f47e…39e5
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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 0x426126a42d…5e740b
Audit this contract →
← previous block·next block →recent activity