← previous blocknext block →recent activity
Analyzing
Block #106,565,128
19 transactions · 18 stateful · 2026-09-20 21:01:17 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,565,128 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w17w011w212w314w015w116w117w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6d87ec7…42eb
0x34b655…2a6f
6 touches
3 conflicts
0x4fbd0a79…626a
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xd25997d0…a689
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x14ea9ada…e627
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 0xf6d87ec76c…cd42eb
Audit this contract →
← previous block·next block →recent activity