← previous blocknext block →recent activity
Analyzing
Block #106,789,880
9 transactions · 9 stateful · 2026-09-21 15:53:26 UTC
Parallelism
44/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,789,880 · 9 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x371b8d95…d138
0x34b655…2a6f
8 touches
6 conflicts
0x1e6832ca…0340
0x34b655…2a6f
8 touches
6 conflicts
0xfbabb02d…af07
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x51087f5a…61f7
0x34b655…2a6f
6 touches
3 conflicts
0x411b5593…fd00
0x34b655…2a6f
4 touches
1 conflict
0x18f16b2b…010a
0x34b655…2a6f
4 touches
1 conflict
0x2391c68a…93a4
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
6 conflicts on slot 0x371b8d9583…62d138
Audit this contract →
← previous block·next block →recent activity