← previous blocknext block →recent activity
Analyzing
Block #106,932,340
36 transactions · 35 stateful · 2026-09-22 03:50:31 UTC
Parallelism
58/100
Blocked
74%
Avg conflicts / tx
2.39
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,932,340 · 36 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
1w02w13w24w05w16w07w09w110w111w212w313w414w515w616w717w818w919w1020w1125w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f396cee…862f
0x34b655…2a6f
18 touches
36 conflicts
0x85bfd0af…ce96
0x34b655…2a6f
16 touches
28 conflicts
0xc7cbc5e5…e7d7
0x34b655…2a6f
14 touches
21 conflicts
0x17b94c2f…869e
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xea2d3331…6e36
0x1b6862…e19c
6 touches
3 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
36 conflicts on slot 0x1f396cee30…ac862f
Audit this contract →
← previous block·next block →recent activity