← previous blocknext block →recent activity
Analyzing
Block #87,513,324
11 transactions · 11 stateful · 2026-07-13 15:40:05 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,513,324 · 11 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
1w05w06w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c46fde6…d6a0
0x34b655…2a6f
4 touches
1 conflict
0xe5620d52…7ede
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0ca12bad…be89
0x34b655…2a6f
2 touches
0 conflicts
0x2be93131…9f74
0x34b655…2a6f
2 touches
0 conflicts
0x2d7ea048…d78e
0x34b655…2a6f
2 touches
0 conflicts
0x3f85f288…7c97
0x34b655…2a6f
2 touches
0 conflicts
0x591d4dcd…33bf
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 0x7c46fde6b8…2fd6a0
Audit this contract →
← previous block·next block →recent activity