← previous blocknext block →recent activity
Analyzing
Block #87,585,878
18 transactions · 16 stateful · 2026-07-13 23:46:02 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,585,878 · 18 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
5w06w19w010w111w213w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x8252706a…7ca5
0x34b655…2a6f
6 touches
3 conflicts
0x25a19347…5424
0x34b655…2a6f
4 touches
1 conflict
0x38d36864…2cb0
0x34b655…2a6f
4 touches
1 conflict
0x3a1edb3e…b841
0x34b655…2a6f
4 touches
1 conflict
0x6b11b9de…f60a
0x34b655…2a6f
4 touches
1 conflict
0x6f58168d…ea24
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity