← previous blocknext block →recent activity
Analyzing
Block #106,917,712
25 transactions · 20 stateful · 2026-09-22 02:36:53 UTC
Parallelism
68/100
Blocked
55%
Avg conflicts / tx
1.4
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,917,712 · 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
1w03w04w05w16w17w213w214w315w417w118w121w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d228d06…6dd6
0x34b655…2a6f
16 touches
28 conflicts
0xd192f4ed…d7ec
0x34b655…2a6f
10 touches
10 conflicts
0x1a62a3a5…ca3a
0x34b655…2a6f
10 touches
10 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
8 touches
6 conflicts
0x050d7a8a…67d0
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x94e7f277…471b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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
28 conflicts on slot 0x7d228d0689…c16dd6
Audit this contract →
← previous block·next block →recent activity