← previous blocknext block →recent activity
Analyzing
Block #87,408,644
11 transactions · 11 stateful · 2026-07-13 03:59:59 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,408,644 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26918bca…6c75
0x34b655…2a6f
8 touches
6 conflicts
0xceb535f3…19cf
0x34b655…2a6f
6 touches
3 conflicts
0xb9f33bff…7bfd
0x34b655…2a6f
6 touches
3 conflicts
0x286711a5…b3bf
0x34b655…2a6f
6 touches
3 conflicts
0x530bc737…5054
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x727fbce7…0c80
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
6 conflicts on slot 0x26918bcabc…d36c75
Audit this contract →
← previous block·next block →recent activity