← previous blocknext block →recent activity
Analyzing
Block #105,850,476
59 transactions · 40 stateful · 2026-09-18 09:03:27 UTC
Parallelism
70/100
Blocked
70%
Avg conflicts / tx
2.69
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #105,850,476 · 59 txs across 18 waves · depth 18
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
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w27w38w49w010w011w112w013w116w118w236w344w1451w1752w254w355w556w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
32 touches
120 conflicts
0xb8dc136f…fb16
0xc8689a…ee79
12 touches
15 conflicts
0x24c5620c…7ac5
0x34b655…2a6f
10 touches
10 conflicts
0x4542f274…9d48
0x34b655…2a6f
10 touches
10 conflicts
0x64a785e4…0110
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x8765edd1…a7d5
0x34b655…2a6f
10 touches
10 conflicts
0x9068a9bc…86ee
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
120 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity