← previous blocknext block →recent activity
Analyzing
Block #106,556,625
23 transactions · 20 stateful · 2026-09-20 20:18:29 UTC
Parallelism
65/100
Blocked
70%
Avg conflicts / tx
2.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,556,625 · 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
1w02w13w04w26w19w210w211w312w413w414w515w616w721w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbf974a4…b232
0x34b655…2a6f
16 touches
28 conflicts
0x8a015e17…d644
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xac0b4a08…faae
0x34b655…2a6f
8 touches
6 conflicts
0xf10f9d72…32e0
0x34b655…2a6f
8 touches
6 conflicts
0x8590b692…b267
0x34b655…2a6f
8 touches
6 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
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 0xdbf974a4cf…a9b232
Audit this contract →
← previous block·next block →recent activity