← previous blocknext block →recent activity
Analyzing
Block #87,703,664
27 transactions · 26 stateful · 2026-07-14 12:53:36 UTC
Parallelism
78/100
Blocked
62%
Avg conflicts / tx
1.37
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,703,664 · 27 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
1w02w14w05w16w28w09w110w211w312w413w520w222w225w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x21605a79…d719
0x34b655…2a6f
8 touches
6 conflicts
0x4f51d069…d0b4
0x34b655…2a6f
8 touches
6 conflicts
0x67905f6e…02a1
0x34b655…2a6f
8 touches
6 conflicts
0x7ae94b74…7aef
0x34b655…2a6f
8 touches
6 conflicts
0xbf68b5d2…0eba
0x34b655…2a6f
8 touches
6 conflicts
0xdfc21d7c…e062
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity