← previous blocknext block →recent activity
Analyzing
Block #105,933,565
24 transactions · 23 stateful · 2026-09-18 16:02:32 UTC
Parallelism
79/100
Blocked
22%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,933,565 · 24 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
1w02w07w08w19w211w315w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b17b0ae…fccf
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x7cbbdd3f…65b0
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x14690632…e9a5
0x34b655…2a6f
2 touches
0 conflicts
0x19f8e68c…4f86
0x34b655…2a6f
2 touches
0 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 0x5b17b0ae3f…05fccf
Audit this contract →
← previous block·next block →recent activity