← previous blocknext block →recent activity
Analyzing
Block #106,550,999
24 transactions · 21 stateful · 2026-09-20 19:50:10 UTC
Parallelism
83/100
Blocked
52%
Avg conflicts / tx
0.92
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,550,999 · 24 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
1w02w13w04w15w16w27w08w19w010w214w015w118w219w220w323w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1cdfe548…d3aa
0x34b655…2a6f
8 touches
6 conflicts
0x03a6ea2e…2b49
0x34b655…2a6f
8 touches
6 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0xb654bd89…a83b
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x28aa2a8b…0f35
0x065c9d…c394
5 touches
3 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
6 conflicts on slot 0x1cdfe54872…bcd3aa
Audit this contract →
← previous block·next block →recent activity