← previous blocknext block →recent activity
Analyzing
Block #87,419,239
20 transactions · 15 stateful · 2026-07-13 05:10:52 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,419,239 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w39w411w519w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e27bdfb…108a
0x34b655…2a6f
10 touches
10 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x194be77e…58ae
0x34b655…2a6f
4 touches
1 conflict
0x19d0eecc…6863
0x34b655…2a6f
4 touches
1 conflict
0x264fa818…9504
0x34b655…2a6f
4 touches
1 conflict
0x337ac160…55bf
0x34b655…2a6f
4 touches
1 conflict
0x3646c884…13db
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0x6e27bdfb04…5c108a
Audit this contract →
← previous block·next block →recent activity