← previous blocknext block →recent activity
Analyzing
Block #87,259,264
10 transactions · 6 stateful · 2026-07-12 11:21:04 UTC
Parallelism
80/100
Blocked
17%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,259,264 · 10 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
1w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x52163873…f09f
0x34b655…2a6f
4 touches
1 conflict
0x6e1b5748…b793
0x34b655…2a6f
4 touches
1 conflict
0x098bfbc0…9995
0x34b655…2a6f
2 touches
0 conflicts
0x0e298091…95a3
0x34b655…2a6f
2 touches
0 conflicts
0x13b8ae8b…6491
0x34b655…2a6f
2 touches
0 conflicts
0x288bc578…318e
0x34b655…2a6f
2 touches
0 conflicts
0x4327afd2…1b3a
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity