← previous blocknext block →recent activity
Analyzing
Block #106,389,185
27 transactions · 26 stateful · 2026-09-20 06:15:45 UTC
Parallelism
70/100
Blocked
54%
Avg conflicts / tx
1.3
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,389,185 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w18w09w111w212w116w218w219w320w421w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf889455…7985
0x34b655…2a6f
12 touches
15 conflicts
0xe283e878…7262
0x34b655…2a6f
10 touches
10 conflicts
0x9dd1656a…dca5
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x6aa624fd…a84d
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
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
15 conflicts on slot 0xbf889455a6…7c7985
Audit this contract →
← previous block·next block →recent activity