← previous blocknext block →recent activity
Analyzing
Block #106,932,387
26 transactions · 26 stateful · 2026-09-22 03:50:45 UTC
Parallelism
62/100
Blocked
54%
Avg conflicts / tx
1.58
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,932,387 · 26 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w17w18w29w310w412w513w614w715w816w923w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51087f5a…61f7
0x34b655…2a6f
14 touches
21 conflicts
0x206f4379…e08a
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0xc01dd830…db33
0x34b655…2a6f
10 touches
10 conflicts
0x799c3770…96ae
0x34b655…2a6f
10 touches
10 conflicts
0x803d32b5…8094
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xc8c615d4…5da3
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0x51087f5abf…f061f7
Audit this contract →
← previous block·next block →recent activity