← previous blocknext block →recent activity
Analyzing
Block #87,497,129
39 transactions · 34 stateful · 2026-07-13 13:51:40 UTC
Parallelism
80/100
Blocked
56%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,497,129 · 39 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w49w010w112w017w118w220w123w327w131w133w434w535w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x326d4924…1788
0x34b655…2a6f
10 touches
10 conflicts
0x54b193ad…c830
0x34b655…2a6f
10 touches
10 conflicts
0x4c188934…158e
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0001
0xc1ff9f…b0fc
10 touches
10 conflicts
0x3ca9a061…1f41
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x206fb8db…a146
0x34b655…2a6f
8 touches
6 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 0x326d4924ab…7f1788
Audit this contract →
← previous block·next block →recent activity