← previous blocknext block →recent activity
Analyzing
Block #87,731,510
39 transactions · 27 stateful · 2026-07-14 16:00:05 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
1.28
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,731,510 · 39 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w110w011w113w015w118w119w220w321w422w523w624w725w835w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0xa55c4598…2988
0x34b655…2a6f
10 touches
10 conflicts
0x8512c35f…696e
0x34b655…2a6f
8 touches
6 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x9ae859db…2d84
0x34b655…2a6f
6 touches
3 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
6 touches
3 conflicts
0x5b145de0…367c
0xc8689a…ee79
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity