← previous blocknext block →recent activity
Analyzing
Block #106,917,144
23 transactions · 23 stateful · 2026-09-22 02:34:02 UTC
Parallelism
78/100
Blocked
52%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,917,144 · 23 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
1w02w13w24w05w36w19w110w213w114w316w217w018w421w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa27a14cf…23d7
0x34b655…2a6f
6 touches
3 conflicts
0xba1edffb…323e
0x34b655…2a6f
6 touches
3 conflicts
0xf1bbd371…e541
0x34b655…2a6f
6 touches
3 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
6 touches
3 conflicts
0xe7306f50…7957
0xd32edf…ff58
5 touches
3 conflicts
0x3af0dd8e…0026
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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 0xa27a14cf51…c623d7
Audit this contract →
← previous block·next block →recent activity