← previous blocknext block →recent activity
Analyzing
Block #106,424,923
24 transactions · 24 stateful · 2026-09-20 09:15:36 UTC
Parallelism
63/100
Blocked
63%
Avg conflicts / tx
1.63
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,424,923 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w18w19w211w312w313w414w515w518w820w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d52cd2f…38f9
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbe9d1d23…3de2
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x8f63f383…6eda
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x0463db49…5d05
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
15 conflicts on slot 0x3d52cd2f68…2338f9
Audit this contract →
← previous block·next block →recent activity