← previous blocknext block →recent activity
Analyzing
Block #106,931,615
22 transactions · 21 stateful · 2026-09-22 03:46:52 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
1.18
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,931,615 · 22 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
2w05w110w211w112w313w414w217w318w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08385adf…0ed3
0x34b655…2a6f
10 touches
10 conflicts
0xc3a899a7…a994
0x34b655…2a6f
10 touches
10 conflicts
0x3e163287…f328
0x34b655…2a6f
10 touches
10 conflicts
0x469dac8d…3411
0x34b655…2a6f
8 touches
6 conflicts
0x858e40c0…7e30
0x34b655…2a6f
8 touches
6 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
8 touches
6 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
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
10 conflicts on slot 0x08385adf4f…740ed3
Audit this contract →
← previous block·next block →recent activity