← previous blocknext block →recent activity
Analyzing
Block #87,792,399
22 transactions · 20 stateful · 2026-07-14 22:47:24 UTC
Parallelism
73/100
Blocked
45%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,792,399 · 22 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
4w05w16w27w310w011w113w215w316w419w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x8d989c17…e984
0x34b655…2a6f
8 touches
6 conflicts
0x9ae859db…2d84
0x34b655…2a6f
6 touches
3 conflicts
0x9fd37234…2731
0x34b655…2a6f
6 touches
3 conflicts
0x2f7060de…7781
0x34b655…2a6f
6 touches
3 conflicts
0x21c9fd73…dae4
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity