← previous blocknext block →recent activity
Analyzing
Block #87,591,721
21 transactions · 20 stateful · 2026-07-14 00:25:07 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,591,721 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w07w18w211w312w013w014w115w117w320w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x1750da27…5388
0x34b655…2a6f
6 touches
3 conflicts
0x1de49243…4aa3
0x34b655…2a6f
6 touches
3 conflicts
0x5b145de0…367c
0xc8689a…ee79
6 touches
3 conflicts
0xa24365bc…5064
0x34b655…2a6f
6 touches
3 conflicts
0xa5c0a528…01b1
0x34b655…2a6f
6 touches
3 conflicts
0xa6b89ebb…a66e
0x34b655…2a6f
6 touches
3 conflicts
0xcd206b7a…abf6
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity