← previous blocknext block →recent activity
Analyzing
Block #87,264,327
14 transactions · 13 stateful · 2026-07-12 11:54:52 UTC
Parallelism
71/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,264,327 · 14 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
5w06w17w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1ed670e…9e0b
0x34b655…2a6f
4 touches
1 conflict
0x8c4f4b8d…ea5f
0x34b655…2a6f
4 touches
1 conflict
0xa7afa3a4…3cd6
0x34b655…2a6f
4 touches
1 conflict
0xa7afa3a4…3cd7
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb35e663e…354e
0x34b655…2a6f
4 touches
1 conflict
0xd770071c…467d
0x34b655…2a6f
4 touches
1 conflict
0x00e21a9f…3583
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
1 conflict on slot 0xe1ed670e1b…a39e0b
Audit this contract →
← previous block·next block →recent activity