← previous blocknext block →recent activity
Analyzing
Block #109,133,828
17 transactions · 13 stateful · 2026-09-29 20:40:35 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #109,133,828 · 17 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
2w03w15w06w17w29w316w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d93ad2c…e747
0x34b655…2a6f
6 touches
3 conflicts
0x65ec5427…5e30
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x1867b653…e61b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x6b267bdf…b173
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
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
3 conflicts on slot 0x3d93ad2c39…a6e747
Audit this contract →
← previous block·next block →recent activity