← previous blocknext block →recent activity
Analyzing
Block #105,633,251
25 transactions · 23 stateful · 2026-09-17 14:48:44 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,633,251 · 25 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
1w03w14w05w06w07w110w111w213w014w116w220w321w424w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x223fb244…a137
0x34b655…2a6f
10 touches
10 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
6 touches
3 conflicts
0xcd93b2d2…30e6
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xdd084cf8…1a71
0x99c7a7…8bf0
4 touches
1 conflict
0x30e75e4f…291b
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0x223fb244b6…1ca137
Audit this contract →
← previous block·next block →recent activity