← previous blocknext block →recent activity
Analyzing
Block #96,030,257
10 transactions · 9 stateful · 2026-08-14 21:56:55 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,030,257 · 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd29144b1…30b5
0x34b655…2a6f
4 touches
1 conflict
0x5e800a72…0189
0x34b655…2a6f
4 touches
1 conflict
0xa3a621f8…75a2
0x34b655…2a6f
4 touches
1 conflict
0xf2774c17…b60c
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
2 touches
0 conflicts
0xcab2c264…3f4d
0x34b655…2a6f
2 touches
0 conflicts
0xd7e54f60…8bd3
0x34b655…2a6f
2 touches
0 conflicts
0xded1a8af…e766
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 0xd29144b18f…9930b5
Audit this contract →
← previous block·next block →recent activity