← previous blocknext block →recent activity
Analyzing
Block #109,056,646
60 transactions · 36 stateful · 2026-09-29 14:11:36 UTC
Parallelism
72/100
Blocked
75%
Avg conflicts / tx
1.85
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #109,056,646 · 60 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w28w39w410w511w614w715w817w318w422w932w1036w237w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
16 touches
28 conflicts
0x7a3d5e6f…7864
0x34b655…2a6f
14 touches
21 conflicts
0xa3f09358…6cde
0x34b655…2a6f
14 touches
21 conflicts
0xeb1b4ae8…64bd
0x37db7f…ec7b
14 touches
21 conflicts
0xc4550172…3d03
0x34b655…2a6f
14 touches
21 conflicts
0xdd9dc4b3…73b8
0x34b655…2a6f
14 touches
21 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
45 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity