← previous blocknext block →recent activity
Analyzing
Block #106,215,925
31 transactions · 30 stateful · 2026-09-19 15:43:47 UTC
Parallelism
65/100
Blocked
70%
Avg conflicts / tx
2.19
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,215,925 · 31 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w28w311w120w421w522w523w624w728w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecf22f58…5939
0x34b655…2a6f
16 touches
28 conflicts
0x05e1eba1…6491
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
12 touches
15 conflicts
0xbf140b24…f052
0x34b655…2a6f
10 touches
10 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0x3865a46d…09f8
0x34b655…2a6f
10 touches
10 conflicts
0x7555b685…0c00
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
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
28 conflicts on slot 0xecf22f58ca…2c5939
Audit this contract →
← previous block·next block →recent activity