← previous blocknext block →recent activity
Analyzing
Block #96,365,212
13 transactions · 13 stateful · 2026-08-16 02:01:41 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,365,212 · 13 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
5w06w17w28w312w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xf40e9839…0001
0x34b655…2a6f
4 touches
1 conflict
0x833f3561…bfd0
0x34b655…2a6f
4 touches
1 conflict
0xc01decc3…08a1
0x34b655…2a6f
4 touches
1 conflict
0xe7d7ea21…039e
0x34b655…2a6f
4 touches
1 conflict
0x00c43e68…2a3c
0x34b655…2a6f
2 touches
0 conflicts
0x0e215b60…b3bb
0x754704…b603
2 touches
0 conflicts
0x3b38d05d…df00
0x754704…b603
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