← previous blocknext block →recent activity
Analyzing
Block #96,324,021
10 transactions · 8 stateful · 2026-08-15 22:34:31 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,324,021 · 10 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
8 touches
6 conflicts
0x925379d7…75b0
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf4db760d…fc5b
0x34b655…2a6f
6 touches
3 conflicts
0xf4db760d…fc5c
0x34b655…2a6f
6 touches
3 conflicts
0x05286dbb…4517
0x34b655…2a6f
6 touches
3 conflicts
0x9d20b779…6b98
0x34b655…2a6f
4 touches
1 conflict
0xa940f3a4…c5e7
0x34b655…2a6f
4 touches
1 conflict
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity