← previous blocknext block →recent activity
Analyzing
Block #109,234,079
28 transactions · 22 stateful · 2026-09-30 05:05:32 UTC
Parallelism
86/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #109,234,079 · 28 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
2w03w04w17w28w316w117w019w124w126w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x336486a4…20bd
0x34b655…2a6f
6 touches
3 conflicts
0x0cc4c914…333b
0x34b655…2a6f
4 touches
1 conflict
0x2249932e…474a
0x34b655…2a6f
4 touches
1 conflict
0x6376cd64…1f1b
0x34b655…2a6f
4 touches
1 conflict
0x7dbeccfc…8faf
0x34b655…2a6f
4 touches
1 conflict
0x898a08aa…c855
0x34b655…2a6f
4 touches
1 conflict
0xa735de1d…29b0
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