← previous blocknext block →recent activity
Analyzing
Block #105,672,848
20 transactions · 20 stateful · 2026-09-17 18:08:04 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,672,848 · 20 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
2w03w15w110w012w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b362527…5809
0x34b655…2a6f
4 touches
1 conflict
0xc10b903d…2f54
0x34b655…2a6f
4 touches
1 conflict
0x88e92ec7…696d
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x7151b1ad…4520
0x34b655…2a6f
2 touches
0 conflicts
0x98783aa8…b36c
0x34b655…2a6f
2 touches
0 conflicts
0xb839a1e8…22b3
0x34b655…2a6f
2 touches
0 conflicts
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 0x2b362527c9…b25809
Audit this contract →
← previous block·next block →recent activity