← previous blocknext block →recent activity
Analyzing
Block #106,569,761
22 transactions · 22 stateful · 2026-09-20 21:24:36 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
1.55
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,569,761 · 22 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
1w03w04w16w07w18w212w314w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6615a36…3cf0
0x34b655…2a6f
16 touches
28 conflicts
0x2b7d52dc…0371
0x34b655…2a6f
8 touches
6 conflicts
0xd7d44415…a1d3
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfe65bb7b…12d7
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0x87ac6e5b…5198
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 0xc6615a36ef…7f3cf0
Audit this contract →
← previous block·next block →recent activity