← previous blocknext block →recent activity
Analyzing
Block #87,420,629
23 transactions · 19 stateful · 2026-07-13 05:20:09 UTC
Parallelism
83/100
Blocked
47%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,420,629 · 23 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
1w02w14w05w17w18w29w311w012w014w115w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe96e3c16…a9f3
0x34b655…2a6f
8 touches
6 conflicts
0x1f006b15…911d
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x6b2ba712…0214
0x34b655…2a6f
6 touches
3 conflicts
0x727fbce7…0c80
0x34b655…2a6f
6 touches
3 conflicts
0xa457c06e…2f06
0x34b655…2a6f
6 touches
3 conflicts
0xcaa1fc83…36e9
0x34b655…2a6f
6 touches
3 conflicts
0xea48da1d…6766
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
6 conflicts on slot 0xe96e3c16e2…cba9f3
Audit this contract →
← previous block·next block →recent activity