← previous blocknext block →recent activity
Analyzing
Block #106,004,162
25 transactions · 20 stateful · 2026-09-18 21:58:01 UTC
Parallelism
68/100
Blocked
55%
Avg conflicts / tx
1.28
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,004,162 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w17w08w110w113w214w015w117w218w319w420w521w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
16 touches
28 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
16 touches
28 conflicts
0x045532dd…4b7d
0x34b655…2a6f
14 touches
21 conflicts
0x7dd96c96…7335
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xd0caf939…ce30
0x34b655…2a6f
8 touches
6 conflicts
0x510dd776…2f09
0x34b655…2a6f
6 touches
3 conflicts
0x5fba4b48…16c0
0x34b655…2a6f
4 touches
1 conflict
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
28 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity