← previous blocknext block →recent activity
Analyzing
Block #105,608,289
20 transactions · 17 stateful · 2026-09-17 12:43:03 UTC
Parallelism
80/100
Blocked
24%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,608,289 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w013w015w116w217w319w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0cbce40b…c4b6
0x34b655…2a6f
8 touches
6 conflicts
0x35b0198e…3e0d
0x34b655…2a6f
6 touches
3 conflicts
0x4118bd12…924a
0x34b655…2a6f
6 touches
3 conflicts
0xc7954a60…d294
0x34b655…2a6f
6 touches
3 conflicts
0x9b924b5c…2ae5
0x34b655…2a6f
4 touches
1 conflict
0x0a2131b3…455e
0x34b655…2a6f
4 touches
1 conflict
0x44163d6b…d475
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
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 0x0cbce40bbe…b5c4b6
Audit this contract →
← previous block·next block →recent activity