← previous blocknext block →recent activity
Analyzing
Block #87,408,863
14 transactions · 14 stateful · 2026-07-13 04:01:27 UTC
Parallelism
64/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,408,863 · 14 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
2w03w14w25w36w09w110w413w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26918bca…6c75
0x34b655…2a6f
6 touches
3 conflicts
0x1a28e34b…1404
0x34b655…2a6f
4 touches
1 conflict
0x1d7140ec…9f87
0x34b655…2a6f
4 touches
1 conflict
0x286711a5…b3bf
0x34b655…2a6f
4 touches
1 conflict
0x3483ab79…8ed3
0x34b655…2a6f
4 touches
1 conflict
0x3f8da809…c1aa
0x34b655…2a6f
4 touches
1 conflict
0x3f99ec8a…334a
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
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
3 conflicts on slot 0x26918bcabc…d36c75
Audit this contract →
← previous block·next block →recent activity