← previous blocknext block →recent activity
Analyzing
Block #87,713,499
20 transactions · 15 stateful · 2026-07-14 13:59:26 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,713,499 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w07w18w29w312w419w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x560ed681…07e6
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xa6389d47…9a28
0x34b655…2a6f
6 touches
3 conflicts
0x36187d32…57e2
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x14fe1598…d0ba
0x34b655…2a6f
2 touches
0 conflicts
0x18c702f8…a14d
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
6 conflicts on slot 0x560ed68159…1e07e6
Audit this contract →
← previous block·next block →recent activity