← previous blocknext block →recent activity
Analyzing
Block #96,449,176
13 transactions · 13 stateful · 2026-08-16 09:03:57 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,449,176 · 13 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46483cb1…e7ca
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0087ca84…0b18
0x34b655…2a6f
2 touches
0 conflicts
0x27c1af7d…e42a
0x34b655…2a6f
2 touches
0 conflicts
0x2937b58c…9cae
0x34b655…2a6f
2 touches
0 conflicts
0x2a0eb1f4…5986
0x34b655…2a6f
2 touches
0 conflicts
0x3d93ad2c…e747
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 0x46483cb14f…c1e7ca
Audit this contract →
← previous block·next block →recent activity