← previous blocknext block →recent activity
Analyzing
Block #105,848,990
39 transactions · 39 stateful · 2026-09-18 08:55:59 UTC
Parallelism
64/100
Blocked
74%
Avg conflicts / tx
2.97
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #105,848,990 · 39 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w16w27w38w19w212w315w116w217w218w419w520w622w823w924w825w926w1028w1229w1335w1037w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x297de2d5…7396
0x34b655…2a6f
16 touches
28 conflicts
0x5d21d97e…aa10
0x34b655…2a6f
14 touches
21 conflicts
0xcaa9e7c9…bc79
0x34b655…2a6f
14 touches
21 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0x97e4c862…4419
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x939cdd56…00c8
0x34b655…2a6f
10 touches
10 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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity