← previous blocknext block →recent activity
Analyzing
Block #96,654,590
17 transactions · 16 stateful · 2026-08-17 02:17:26 UTC
Parallelism
82/100
Blocked
19%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,654,590 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w18w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b2d3bee…8eeb
0x34b655…2a6f
6 touches
3 conflicts
0x0a3dfe51…3b76
0x34b655…2a6f
4 touches
1 conflict
0x0a3dfe51…3b77
0x34b655…2a6f
4 touches
1 conflict
0x2dd03fb9…6243
0x34b655…2a6f
4 touches
1 conflict
0x3b6e959d…158f
0x34b655…2a6f
4 touches
1 conflict
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0x3f24a8ec…24e1
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 0x9b2d3bee9d…d68eeb
Audit this contract →
← previous block·next block →recent activity