← previous blocknext block →recent activity
Analyzing
Block #96,022,532
14 transactions · 12 stateful · 2026-08-14 21:18:04 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,022,532 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w07w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x12bf5c77…5588
0x34b655…2a6f
6 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x065edde0…73a8
0x34b655…2a6f
2 touches
0 conflicts
0x2c8f52ce…fe9a
0x34b655…2a6f
2 touches
0 conflicts
0x31616f97…1acc
0x34b655…2a6f
2 touches
0 conflicts
0x71f35abd…6a3f
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity