← previous blocknext block →recent activity
Analyzing
Block #96,654,903
10 transactions · 10 stateful · 2026-08-17 02:19:00 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,654,903 · 10 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
2w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4755fafb…859b
0x34b655…2a6f
4 touches
1 conflict
0xf0d45ffd…89cf
0x34b655…2a6f
4 touches
1 conflict
0x68c07cb9…ae14
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x203f132b…89fc
0x34b655…2a6f
2 touches
0 conflicts
0x433ec3a1…a1e8
0x34b655…2a6f
2 touches
0 conflicts
0x58888587…bb8d
0x34b655…2a6f
2 touches
0 conflicts
0x7fb99184…e8bb
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 0x4755fafb14…12859b
Audit this contract →
← previous block·next block →recent activity