← previous blocknext block →recent activity
Analyzing
Block #105,844,960
20 transactions · 19 stateful · 2026-09-18 08:35:41 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,844,960 · 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
1w02w13w14w26w07w19w211w312w014w218w119w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90f1f852…b879
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
6 touches
3 conflicts
0xf8ec7381…bfbb
0x34b655…2a6f
6 touches
3 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
6 touches
3 conflicts
0x6183ee9a…21b1
0x34b655…2a6f
4 touches
1 conflict
0x90a021f0…f922
0x34b655…2a6f
4 touches
1 conflict
0x972d73b6…da8b
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
3 conflicts on slot 0x90f1f852b0…edb879
Audit this contract →
← previous block·next block →recent activity