← previous blocknext block →recent activity
Analyzing
Block #105,581,845
21 transactions · 21 stateful · 2026-09-17 10:29:56 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,581,845 · 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
3w04w15w28w212w314w415w518w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe63962ff…a47d
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x9210e826…1414
0x34b655…2a6f
6 touches
3 conflicts
0x0efc210e…70ab
0x34b655…2a6f
6 touches
3 conflicts
0x89999c15…fdac
0x34b655…2a6f
6 touches
3 conflicts
0x232df012…c608
0x34b655…2a6f
6 touches
3 conflicts
0xd5910f79…033c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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
15 conflicts on slot 0xe63962ff9c…bba47d
Audit this contract →
← previous block·next block →recent activity