← previous blocknext block →recent activity
Analyzing
Block #109,233,601
20 transactions · 16 stateful · 2026-09-30 05:03:07 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #109,233,601 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w29w315w016w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
4 touches
1 conflict
0xe2d50773…c39e
0x34b655…2a6f
4 touches
1 conflict
0x238d0a65…428b
0x37db7f…ec7b
4 touches
1 conflict
0xeb1b4ae8…64bd
0x37db7f…ec7b
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x1032f16c…a9b1
0x34b655…2a6f
4 touches
1 conflict
0x23f3acc7…dbea
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity