← previous blocknext block →recent activity
Analyzing
Block #105,366,233
16 transactions · 16 stateful · 2026-09-16 16:24:44 UTC
Parallelism
81/100
Blocked
19%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,366,233 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w07w110w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x77551a1f…a238
0x34b655…2a6f
4 touches
1 conflict
0x2c44ac96…cf9c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xccb84072…2d98
0x34b655…2a6f
4 touches
1 conflict
0xd35f502b…ae0d
0x34b655…2a6f
4 touches
1 conflict
0xe2c4da1c…0e41
0x34b655…2a6f
4 touches
1 conflict
0xe2c4da1c…0e42
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
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
1 conflict on slot 0x77551a1fd6…f7a238
Audit this contract →
← previous block·next block →recent activity