← previous blocknext block →recent activity
Analyzing
Block #87,291,857
16 transactions · 14 stateful · 2026-07-12 14:58:59 UTC
Parallelism
63/100
Blocked
57%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,291,857 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w38w29w310w411w512w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc94dfe1…0b3d
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1ab
0xb1dbf0…c0d3
6 touches
3 conflicts
0xa2ea76a0…a726
0x34b655…2a6f
6 touches
3 conflicts
0x07b979bc…3564
0xb1dbf0…c0d3
4 touches
1 conflict
0x6286219a…0721
0xb1dbf0…c0d3
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 0xbc94dfe1d8…a70b3d
Audit this contract →
← previous block·next block →recent activity