← previous blocknext block →recent activity
Analyzing
Block #87,524,893
18 transactions · 15 stateful · 2026-07-13 16:58:01 UTC
Parallelism
56/100
Blocked
60%
Avg conflicts / tx
1.61
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,524,893 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w37w38w49w510w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfdd655b8…bf89
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x2b4f426d…5de5
0x34b655…2a6f
8 touches
6 conflicts
0x502b3ee1…7f7b
0x34b655…2a6f
8 touches
6 conflicts
0x53f393fa…00b9
0x34b655…2a6f
8 touches
6 conflicts
0xfd101fa5…fd9a
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0xfdd655b80c…53bf89
Audit this contract →
← previous block·next block →recent activity