← previous blocknext block →recent activity
Analyzing
Block #87,419,313
7 transactions · 6 stateful · 2026-07-13 05:11:22 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,419,313 · 7 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd330c0c5…6f64
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x16649a8b…40b0
0x34b655…2a6f
2 touches
0 conflicts
0x16649a8b…40b1
0x34b655…2a6f
2 touches
0 conflicts
0x19d0eecc…6863
0x34b655…2a6f
2 touches
0 conflicts
0x52d2a422…f1ea
0x34b655…2a6f
2 touches
0 conflicts
0x595cbd16…dac4
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 0xd330c0c595…b26f64
Audit this contract →
← previous block·next block →recent activity