← previous blocknext block →recent activity
Analyzing
Block #87,329,449
19 transactions · 17 stateful · 2026-07-12 19:10:20 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,329,449 · 19 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
1w02w14w05w16w07w28w310w012w113w217w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4aa41e0…f123
0x34b655…2a6f
10 touches
10 conflicts
0x851ff3c1…1b15
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x687a9363…cc03
0x34b655…2a6f
6 touches
3 conflicts
0xae38319d…6a67
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
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
10 conflicts on slot 0xb4aa41e0a7…88f123
Audit this contract →
← previous block·next block →recent activity