← previous blocknext block →recent activity
Analyzing
Block #106,235,618
20 transactions · 17 stateful · 2026-09-19 17:22:56 UTC
Parallelism
80/100
Blocked
41%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,235,618 · 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
1w02w13w04w05w16w112w013w216w318w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a84e266…4f8a
0x34b655…2a6f
6 touches
3 conflicts
0xc3e72796…a3ca
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x6aa624fd…a852
0x1b6862…e19c
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 0x1a84e266a3…f64f8a
Audit this contract →
← previous block·next block →recent activity