← previous blocknext block →recent activity
Analyzing
Block #105,748,888
23 transactions · 22 stateful · 2026-09-18 00:30:45 UTC
Parallelism
52/100
Blocked
50%
Avg conflicts / tx
2.04
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #105,748,888 · 23 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w09w110w212w313w314w415w516w617w718w821w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
20 touches
45 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x416ce558…38d2
0x34b655…2a6f
8 touches
6 conflicts
0x213b816c…a5e0
0x34b655…2a6f
8 touches
6 conflicts
0x232df012…c608
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x790debba…6bf8
0x34b655…2a6f
6 touches
3 conflicts
0x27034002…2f27
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
45 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity