← previous blocknext block →recent activity
Analyzing
Block #106,917,249
61 transactions · 50 stateful · 2026-09-22 02:34:33 UTC
Parallelism
72/100
Blocked
78%
Avg conflicts / tx
2.49
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,917,249 · 61 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
1w02w03w110w111w215w116w218w322w524w625w727w235w437w238w339w440w541w642w743w849w151w257w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x94e7f277…471b
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xe06d2b07…cdd0
0x34b655…2a6f
14 touches
21 conflicts
0xba1edffb…323e
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
14 touches
21 conflicts
0xa0998a89…1f5a
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity