← previous blocknext block →recent activity
Analyzing
Block #96,665,691
11 transactions · 9 stateful · 2026-08-17 03:13:15 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,665,691 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xb2fa1675…4e07
0x34b655…2a6f
4 touches
1 conflict
0xfbe6a366…8ca1
0x34b655…2a6f
4 touches
1 conflict
0x0af9b708…ae17
0x34b655…2a6f
2 touches
0 conflicts
0x16839256…371f
0x34b655…2a6f
2 touches
0 conflicts
0x1a5d321d…a474
0x34b655…2a6f
2 touches
0 conflicts
0x2d94ecd9…43db
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity