← previous blocknext block →recent activity
Analyzing
Block #96,482,743
9 transactions · 7 stateful · 2026-08-16 11:52:48 UTC
Parallelism
44/100
Blocked
57%
Avg conflicts / tx
1.11
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,482,743 · 9 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
1w02w14w25w36w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xcbda32af…5a25
0x34b655…2a6f
8 touches
6 conflicts
0x6a8d8180…0ae3
0x34b655…2a6f
6 touches
3 conflicts
0x2fceaa3d…d516
0x34b655…2a6f
4 touches
1 conflict
0xaf50fd64…63f3
0x34b655…2a6f
4 touches
1 conflict
0xd3985e87…e0ec
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
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
10 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity