← previous blocknext block →recent activity
Analyzing
Block #87,264,479
30 transactions · 23 stateful · 2026-07-12 11:55:53 UTC
Parallelism
87/100
Blocked
39%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,264,479 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w08w114w015w116w117w018w119w222w323w224w325w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xf8c9546a…ebba
0x34b655…2a6f
6 touches
3 conflicts
0xbaf991af…3033
0x34b655…2a6f
6 touches
3 conflicts
0xa71076a8…ff4e
0x065c9d…c394
5 touches
3 conflicts
0xdb08c4c0…b787
0xd32edf…ff58
5 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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity