← previous blocknext block →recent activity
Analyzing
Block #87,349,063
19 transactions · 15 stateful · 2026-07-12 21:21:28 UTC
Parallelism
58/100
Blocked
47%
Avg conflicts / tx
1.16
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,349,063 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w514w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x727fbce7…0c80
0x34b655…2a6f
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0xc368d7fd…aaec
0x34b655…2a6f
14 touches
21 conflicts
0x922c7ebd…6600
0xc8689a…ee79
12 touches
15 conflicts
0x7506443a…4820
0x34b655…2a6f
12 touches
15 conflicts
0x7523ad90…2ba5
0x34b655…2a6f
12 touches
15 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
12 touches
15 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
21 conflicts on slot 0x727fbce74b…da0c80
Audit this contract →
← previous block·next block →recent activity