← previous blocknext block →recent activity
Analyzing
Block #87,729,438
20 transactions · 20 stateful · 2026-07-14 15:46:14 UTC
Parallelism
65/100
Blocked
35%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,729,438 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w38w49w514w616w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94ba9c4a…41d8
0x34b655…2a6f
12 touches
15 conflicts
0x954aad92…7358
0x34b655…2a6f
8 touches
6 conflicts
0x085df2c1…305a
0x34b655…2a6f
8 touches
6 conflicts
0x75ac5fa0…1808
0x34b655…2a6f
8 touches
6 conflicts
0xf31b6b3f…055e
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x8a705be8…7ac4
0xc8689a…ee79
6 touches
3 conflicts
0x48de9cd5…2f4c
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
15 conflicts on slot 0x94ba9c4a07…0c41d8
Audit this contract →
← previous block·next block →recent activity