← previous blocknext block →recent activity
Analyzing
Block #106,545,450
17 transactions · 13 stateful · 2026-09-20 19:22:15 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,545,450 · 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
1w02w13w07w08w110w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76ed17bf…9bd8
0x34b655…2a6f
8 touches
6 conflicts
0x1715a62a…7b93
0x34b655…2a6f
8 touches
6 conflicts
0xd911522b…e960
0x34b655…2a6f
6 touches
3 conflicts
0x9dd0a735…4d04
0x34b655…2a6f
4 touches
1 conflict
0x5655f5c3…6b75
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x2a2896a0…2a0a
0x34b655…2a6f
4 touches
1 conflict
0xfe2577ac…677b
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
6 conflicts on slot 0x76ed17bfaa…199bd8
Audit this contract →
← previous block·next block →recent activity