← previous blocknext block →recent activity
Analyzing
Block #87,615,275
49 transactions · 36 stateful · 2026-07-14 03:02:38 UTC
Parallelism
71/100
Blocked
67%
Avg conflicts / tx
2.1
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,615,275 · 49 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
1w02w04w06w17w28w09w111w012w119w020w121w222w323w424w525w626w727w828w931w1032w234w1135w1236w137w344w1145w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0xc6ed530e…fa7d
0x34b655…2a6f
10 touches
10 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
10 touches
10 conflicts
0xe197e523…ef9c
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x4c188934…158e
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xc514314c…1aa4
0x34b655…2a6f
8 touches
6 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