← previous blocknext block →recent activity
Analyzing
Block #106,934,720
20 transactions · 18 stateful · 2026-09-22 04:02:29 UTC
Parallelism
65/100
Blocked
39%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,934,720 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w09w010w111w212w313w414w515w616w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8590b692…b267
0x34b655…2a6f
12 touches
15 conflicts
0x7ca519d1…4f93
0x34b655…2a6f
10 touches
10 conflicts
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0x9375a764…dca1
0x34b655…2a6f
6 touches
3 conflicts
0x7b92b5ef…9f17
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x51087f5a…61f7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
15 conflicts on slot 0x8590b69238…6ab267
Audit this contract →
← previous block·next block →recent activity