← previous blocknext block →recent activity
Analyzing
Block #87,591,503
40 transactions · 30 stateful · 2026-07-14 00:23:39 UTC
Parallelism
65/100
Blocked
73%
Avg conflicts / tx
2.23
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,591,503 · 40 txs across 14 waves · depth 14
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
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w114w215w016w317w418w520w621w722w823w924w1026w1127w428w1029w230w1131w332w433w534w638w1239w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
14 touches
21 conflicts
0x1de49243…4aa3
0x34b655…2a6f
10 touches
10 conflicts
0x2d8a87f4…9991
0x34b655…2a6f
10 touches
10 conflicts
0x5e3a31d1…7a6e
0x34b655…2a6f
10 touches
10 conflicts
0x7d7ff6bb…f729
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x1750da27…5388
0x34b655…2a6f
10 touches
10 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
45 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity