← previous blocknext block →recent activity
Analyzing
Block #96,826,282
10 transactions · 9 stateful · 2026-08-17 16:40:59 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,826,282 · 10 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
2w04w05w16w27w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
6 touches
3 conflicts
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0xf275b4ca…57b8
0xe52b14…7230
4 touches
1 conflict
0x82a81399…58a2
0x34b655…2a6f
3 touches
1 conflict
0xde2b7743…8567
0xe52b14…7230
3 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
2 touches
0 conflicts
0x7aad02c6…b979
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: 0xe52b1424…bb7230
3 conflicts on slot 0xf79df061c7…91e005
Audit this contract →
← previous block·next block →recent activity