← previous blocknext block →recent activity
Analyzing
Block #87,710,604
45 transactions · 38 stateful · 2026-07-14 13:40:04 UTC
Parallelism
71/100
Blocked
61%
Avg conflicts / tx
1.69
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,710,604 · 45 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
1w02w13w04w17w09w010w111w213w114w216w217w320w421w527w131w234w335w436w537w540w942w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x3464bbc5…a323
0xa6afd3…d132
10 touches
10 conflicts
0x1803586e…d149
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x07d8b1e8…78c6
0x34b655…2a6f
8 touches
6 conflicts
0x8fe37a3f…4c89
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf4f4af3b…c5bd
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity