← previous blocknext block →recent activity
Analyzing
Block #87,504,427
36 transactions · 24 stateful · 2026-07-13 14:40:33 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,504,427 · 36 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
1w02w17w08w017w018w119w220w324w125w026w127w030w333w434w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf06ab8d8…3589
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x4c04ce68…d007
0x34b655…2a6f
6 touches
3 conflicts
0x861e5aef…d32c
0x34b655…2a6f
6 touches
3 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0xe5a38e46…a68c
0x34b655…2a6f
6 touches
3 conflicts
0x1280f157…ac8e
0x34b655…2a6f
6 touches
3 conflicts
0x61043b15…aca5
0x34b655…2a6f
4 touches
1 conflict
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 0xf06ab8d81b…9b3589
Audit this contract →
← previous block·next block →recent activity