← previous blocknext block →recent activity
Analyzing
Block #105,625,890
13 transactions · 13 stateful · 2026-09-17 14:11:40 UTC
Parallelism
54/100
Blocked
54%
Avg conflicts / tx
1.08
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,625,890 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w38w211w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xa30eb1f7…f285
0x34b655…2a6f
6 touches
3 conflicts
0x3c4b8fbd…9354
0x34b655…2a6f
4 touches
1 conflict
0x506cf70a…e07a
0x34b655…2a6f
4 touches
1 conflict
0x5e3a31d1…7a6e
0x34b655…2a6f
4 touches
1 conflict
0x647d1760…99f7
0x34b655…2a6f
4 touches
1 conflict
0x8c5b02c0…2e16
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
6 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity