← previous blocknext block →recent activity
Analyzing
Block #87,731,381
15 transactions · 14 stateful · 2026-07-14 15:59:13 UTC
Parallelism
60/100
Blocked
43%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,731,381 · 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
1w02w14w25w36w410w514w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80fd3987…2314
0x34b655…2a6f
10 touches
10 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
10 touches
10 conflicts
0xe6fd79d8…6136
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xe40c96f3…9ce4
0x34b655…2a6f
6 touches
3 conflicts
0xf28cf8dc…b0ca
0x34b655…2a6f
6 touches
3 conflicts
0xfcb950e3…7273
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
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
10 conflicts on slot 0x80fd398747…852314
Audit this contract →
← previous block·next block →recent activity