← previous blocknext block →recent activity
Analyzing
Block #109,056,720
39 transactions · 35 stateful · 2026-09-29 14:11:59 UTC
Parallelism
54/100
Blocked
57%
Avg conflicts / tx
4.08
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #109,056,720 · 39 txs across 18 waves · depth 18
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1214w1315w1416w1522w1637w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
34 touches
136 conflicts
0xc4550172…3d03
0x34b655…2a6f
34 touches
136 conflicts
0x7a3d5e6f…7864
0x34b655…2a6f
32 touches
120 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
32 touches
120 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
32 touches
120 conflicts
0xd275ed99…2e99
0x34b655…2a6f
32 touches
120 conflicts
0xdd9dc4b3…73b8
0x34b655…2a6f
32 touches
120 conflicts
0xfc8c9734…8019
0x34b655…2a6f
32 touches
120 conflicts
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
136 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity