← previous blocknext block →recent activity
Analyzing
Block #106,464,186
17 transactions · 16 stateful · 2026-09-20 12:33:16 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,464,186 · 17 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
1w04w05w18w110w011w212w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x206a4507…e6c3
0x34b655…2a6f
6 touches
3 conflicts
0xee46716c…d788
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe098738f…9bbe
0x34b655…2a6f
4 touches
1 conflict
0xebf19faa…72cb
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
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 0x206a4507f8…79e6c3
Audit this contract →
← previous block·next block →recent activity