← previous blocknext block →recent activity
Analyzing
Block #106,533,081
50 transactions · 37 stateful · 2026-09-20 18:20:00 UTC
Parallelism
70/100
Blocked
73%
Avg conflicts / tx
2.86
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,533,081 · 50 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w19w010w111w012w114w222w325w426w529w630w731w832w933w1034w1135w1236w1337w1442w243w349w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
30 touches
105 conflicts
0xcf94604f…25e6
0x34b655…2a6f
14 touches
21 conflicts
0xb8dc136f…fb16
0xc8689a…ee79
14 touches
21 conflicts
0x100ec7e6…6b5a
0x34b655…2a6f
14 touches
21 conflicts
0xdb3937e8…23cb
0x34b655…2a6f
14 touches
21 conflicts
0x8765edd1…a7d5
0x34b655…2a6f
14 touches
21 conflicts
0xc102b2b7…57a2
0x34b655…2a6f
14 touches
21 conflicts
0x1ea4da44…a461
0x37db7f…ec7b
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
105 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity