← previous blocknext block →recent activity
Analyzing
Block #105,855,866
22 transactions · 20 stateful · 2026-09-18 09:30:35 UTC
Parallelism
50/100
Blocked
60%
Avg conflicts / tx
2.23
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #105,855,866 · 22 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
1w02w13w04w111w212w313w414w515w516w617w718w820w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe11ef64…754d
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xfefb0189…f726
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xbc53769f…f5b2
0x34b655…2a6f
8 touches
6 conflicts
0x81ca8c9e…28cb
0x34b655…2a6f
6 touches
3 conflicts
0x297de2d5…7396
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
36 conflicts on slot 0xbe11ef64c0…8b754d
Audit this contract →
← previous block·next block →recent activity