← previous blocknext block →recent activity
Analyzing
Block #87,499,017
15 transactions · 14 stateful · 2026-07-13 14:04:18 UTC
Parallelism
60/100
Blocked
57%
Avg conflicts / tx
1.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,499,017 · 15 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
1w02w03w14w25w36w47w59w010w011w112w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xeeb97f3b…a204
0x34b655…2a6f
10 touches
10 conflicts
0x63c900f4…2600
0x34b655…2a6f
10 touches
10 conflicts
0xf8a46a04…d63a
0x34b655…2a6f
10 touches
10 conflicts
0x6b2ba712…0214
0x34b655…2a6f
8 touches
6 conflicts
0x727fbce7…0c80
0x34b655…2a6f
8 touches
6 conflicts
0x76e8f40a…530e
0x34b655…2a6f
8 touches
6 conflicts
0x8910d46f…cc7d
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity