← previous blocknext block →recent activity
Analyzing
Block #95,984,961
14 transactions · 13 stateful · 2026-08-14 18:08:57 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,984,961 · 14 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
1w02w03w14w15w06w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x35a9f06c…7689
0x34b655…2a6f
4 touches
1 conflict
0x2cf02ca9…f960
0x34b655…2a6f
2 touches
0 conflicts
0x859fe39d…effa
0x34b655…2a6f
2 touches
0 conflicts
0x868d81dd…8ad5
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity