← previous blocknext block →recent activity
Analyzing
Block #105,760,547
26 transactions · 25 stateful · 2026-09-18 01:29:25 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,760,547 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w16w27w08w114w015w119w320w421w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe171048c…27c2
0x34b655…2a6f
8 touches
6 conflicts
0xaf9dbf3b…f9ec
0x34b655…2a6f
8 touches
6 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
8 touches
6 conflicts
0x953517cb…cdec
0x34b655…2a6f
6 touches
3 conflicts
0x31f9ad94…7ef3
0x34b655…2a6f
6 touches
3 conflicts
0x9c2fc330…0091
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
6 conflicts on slot 0xe171048c4a…f327c2
Audit this contract →
← previous block·next block →recent activity