← previous blocknext block →recent activity
Analyzing
Block #87,285,911
50 transactions · 46 stateful · 2026-07-12 14:19:13 UTC
Parallelism
88/100
Blocked
54%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,285,911 · 50 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
1w02w05w08w09w111w012w113w114w016w217w118w119w220w021w122w223w324w125w226w327w442w143w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x358a6871…af7c
0xd32edf…ff58
9 touches
10 conflicts
0x52e69143…95ad
0x065c9d…c394
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity