← previous blocknext block →recent activity
Analyzing
Block #87,487,817
39 transactions · 34 stateful · 2026-07-13 12:49:21 UTC
Parallelism
67/100
Blocked
76%
Avg conflicts / tx
2.31
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,487,817 · 39 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w18w09w112w013w114w215w316w417w518w619w220w322w423w530w1031w1132w433w337w438w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…0001
0xc1ff9f…b0fc
14 touches
21 conflicts
0x734ee320…caae
0x34b655…2a6f
10 touches
10 conflicts
0xb9266685…8b1d
0x34b655…2a6f
10 touches
10 conflicts
0xd672bfc0…1ed0
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x4c04ce68…d007
0x34b655…2a6f
8 touches
6 conflicts
0xa57576bb…e01f
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity