← previous blocknext block →recent activity
Analyzing
Block #105,627,557
20 transactions · 19 stateful · 2026-09-17 14:20:04 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,627,557 · 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
1w02w13w04w15w16w27w08w110w211w012w114w316w019w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x045532dd…4b7d
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0xb5811949…acae
0x34b655…2a6f
8 touches
6 conflicts
0x678143da…dc6b
0x34b655…2a6f
6 touches
3 conflicts
0x15ff275d…8fd8
0x34b655…2a6f
6 touches
3 conflicts
0xa4f37e6f…85d5
0x34b655…2a6f
5 touches
3 conflicts
0xf8480e2a…dff1
0x1b6862…e19c
4 touches
1 conflict
0x11d4fcce…6d2d
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 0x045532dd4b…244b7d
Audit this contract →
← previous block·next block →recent activity