← previous blocknext block →recent activity
Analyzing
Block #96,389,216
10 transactions · 8 stateful · 2026-08-16 04:02:25 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,389,216 · 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
2w04w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe39a1f7…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0x232f95c2…1d16
0x34b655…2a6f
4 touches
1 conflict
0x5adda4a7…b840
0x34b655…2a6f
4 touches
1 conflict
0x044844a0…7418
0x34b655…2a6f
2 touches
0 conflicts
0x9b2d3bee…8eec
0x34b655…2a6f
2 touches
0 conflicts
0x0b9b07b8…b998
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 0xfe39a1f75c…758eb0
Audit this contract →
← previous block·next block →recent activity