← previous blocknext block →recent activity
Analyzing
Block #87,718,113
21 transactions · 18 stateful · 2026-07-14 14:30:28 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.43
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,718,113 · 21 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
1w02w03w14w25w36w413w514w119w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x2697123c…8526
0x34b655…2a6f
12 touches
15 conflicts
0x7525206c…fbd5
0x34b655…2a6f
12 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x67905f6e…02a1
0x34b655…2a6f
10 touches
10 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
10 touches
10 conflicts
0xf04687a1…5ffa
0x34b655…2a6f
10 touches
10 conflicts
0x4d64ffdd…ecd8
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity