← previous blocknext block →recent activity
Analyzing
Block #106,307,768
21 transactions · 14 stateful · 2026-09-19 23:26:01 UTC
Parallelism
76/100
Blocked
43%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,307,768 · 21 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
1w04w18w09w210w111w212w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65903ef9…2567
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x612b5b5d…78b9
0x34b655…2a6f
6 touches
3 conflicts
0x5164ab0e…01e1
0xc8689a…ee79
6 touches
3 conflicts
0x32cfcaed…9b9b
0x34b655…2a6f
6 touches
3 conflicts
0xcd6e4b1d…cc89
0x34b655…2a6f
6 touches
3 conflicts
0x2a8bc05a…0464
0x37db7f…ec7b
6 touches
3 conflicts
0xdbcc4ab8…2aba
0x37db7f…ec7b
6 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 0x65903ef9a0…7d2567
Audit this contract →
← previous block·next block →recent activity