← previous blocknext block →recent activity
Analyzing
Block #87,732,731
22 transactions · 21 stateful · 2026-07-14 16:08:15 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,732,731 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w09w010w011w114w116w219w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa55c4598…2988
0x34b655…2a6f
12 touches
15 conflicts
0x67905f6e…02a1
0x34b655…2a6f
8 touches
6 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x3726966a…669d
0x34b655…2a6f
8 touches
6 conflicts
0x805d08cf…3cfc
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x741fa213…dde8
0x34b655…2a6f
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
15 conflicts on slot 0xa55c45989b…e52988
Audit this contract →
← previous block·next block →recent activity