← previous blocknext block →recent activity
Analyzing
Block #87,518,661
21 transactions · 20 stateful · 2026-07-13 16:15:54 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,518,661 · 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
2w03w15w06w17w08w19w210w312w114w215w316w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0eac6378…36f4
0x34b655…2a6f
8 touches
6 conflicts
0x2b5101ac…090b
0x34b655…2a6f
8 touches
6 conflicts
0x1eb0fab5…3517
0x34b655…2a6f
8 touches
6 conflicts
0x9d9bed71…d466
0x34b655…2a6f
8 touches
6 conflicts
0xd2904968…8420
0x34b655…2a6f
8 touches
6 conflicts
0xe7d2a532…f5a5
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x796c1a47…2bfb
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 0x0eac637818…cb36f4
Audit this contract →
← previous block·next block →recent activity