← previous blocknext block →recent activity
Analyzing
Block #105,644,085
39 transactions · 32 stateful · 2026-09-17 15:43:16 UTC
Parallelism
82/100
Blocked
66%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,644,085 · 39 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w16w210w217w229w330w433w334w435w436w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xa6661639…f0ef
0x34b655…2a6f
10 touches
10 conflicts
0x84f65aa2…3f51
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x0463db49…5d05
0x34b655…2a6f
8 touches
6 conflicts
0x0a809ce1…7894
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x544745e8…d72e
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity