← previous blocknext block →recent activity
Analyzing
Block #87,617,079
14 transactions · 11 stateful · 2026-07-14 03:14:42 UTC
Parallelism
86/100
Blocked
9%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,617,079 · 14 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
6w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ed58b36…c5e5
0x34b655…2a6f
4 touches
1 conflict
0xca3f1796…927c
0x34b655…2a6f
4 touches
1 conflict
0x46279ae7…20dd
0x2b46c0…1669
2 touches
0 conflicts
0x7f4a8466…f2cc
0x2b46c0…1669
2 touches
0 conflicts
0x0b88e8b5…76e2
0x34b655…2a6f
2 touches
0 conflicts
0x0edff147…13ed
0x34b655…2a6f
2 touches
0 conflicts
0x0edff147…13ee
0x34b655…2a6f
2 touches
0 conflicts
0x70e53a46…9b91
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 0x5ed58b3680…35c5e5
Audit this contract →
← previous block·next block →recent activity