← previous blocknext block →recent activity
Analyzing
Block #106,953,414
23 transactions · 21 stateful · 2026-09-22 05:36:36 UTC
Parallelism
65/100
Blocked
57%
Avg conflicts / tx
1.61
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,953,414 · 23 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
1w02w03w04w15w26w28w111w212w317w418w519w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x82c4cda4…0ebf
0x34b655…2a6f
14 touches
21 conflicts
0x67287ef9…2d07
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x9375a764…dca1
0x34b655…2a6f
8 touches
6 conflicts
0xab41643c…f9bf
0x34b655…2a6f
8 touches
6 conflicts
0x6a14baa3…c6e9
0x34b655…2a6f
8 touches
6 conflicts
0xc9279af8…5894
0x34b655…2a6f
6 touches
3 conflicts
0xab981df1…2941
0x34b655…2a6f
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
21 conflicts on slot 0x82c4cda410…4b0ebf
Audit this contract →
← previous block·next block →recent activity