← previous blocknext block →recent activity
Analyzing
Block #105,852,761
21 transactions · 19 stateful · 2026-09-18 09:14:58 UTC
Parallelism
67/100
Blocked
32%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,852,761 · 21 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
8w012w113w214w315w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3a467d1…c539
0x34b655…2a6f
14 touches
21 conflicts
0x55192654…91fe
0x34b655…2a6f
12 touches
15 conflicts
0x5b6af007…0f35
0x34b655…2a6f
10 touches
10 conflicts
0xd79c9727…1233
0x34b655…2a6f
8 touches
6 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0xe3a467d18d…a8c539
Audit this contract →
← previous block·next block →recent activity