← previous blocknext block →recent activity
Analyzing
Block #96,784,396
14 transactions · 14 stateful · 2026-08-17 13:10:18 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,784,396 · 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
1w02w19w010w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf509a8c6…0ab1
0x34b655…2a6f
4 touches
1 conflict
0xf8a748aa…446a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xdf93c009…d51f
0x851145…3f07
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x2bac71c3…3296
0x34b655…2a6f
2 touches
0 conflicts
0x2f29153d…cae9
0x34b655…2a6f
2 touches
0 conflicts
0x3046f8a8…e6ea
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 0xf509a8c6cd…9b0ab1
Audit this contract →
← previous block·next block →recent activity