← previous blocknext block →recent activity
Analyzing
Block #106,198,966
23 transactions · 20 stateful · 2026-09-19 14:18:22 UTC
Parallelism
65/100
Blocked
40%
Avg conflicts / tx
1.26
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,198,966 · 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
2w09w110w213w315w416w517w618w722w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ec53e25…569f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x5717771c…45ed
0x34b655…2a6f
12 touches
15 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
8 touches
6 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x89bcc1d2…0ea0
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x3ec53e253d…80569f
Audit this contract →
← previous block·next block →recent activity