← previous blocknext block →recent activity
Analyzing
Block #96,299,275
10 transactions · 9 stateful · 2026-08-15 20:30:03 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,299,275 · 10 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
1w04w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x9f60dbd0…5f36
0x34b655…2a6f
4 touches
1 conflict
0x1ac1c6bd…58eb
0x34b655…2a6f
2 touches
0 conflicts
0x39d71ab5…c230
0x34b655…2a6f
2 touches
0 conflicts
0x424934c8…f2f1
0x34b655…2a6f
2 touches
0 conflicts
0x5f7d122d…f965
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 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity