← previous blocknext block →recent activity
Analyzing
Block #87,408,823
34 transactions · 30 stateful · 2026-07-13 04:01:10 UTC
Parallelism
82/100
Blocked
63%
Avg conflicts / tx
1.26
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,408,823 · 34 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
1w02w04w05w16w17w28w09w111w012w113w114w215w316w417w521w323w424w525w128w129w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x34731dbd…e467
0x34b655…2a6f
10 touches
10 conflicts
0x00842ba8…bdc6
0x34b655…2a6f
10 touches
10 conflicts
0x734ee320…caae
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf8c9546a…ebba
0x34b655…2a6f
8 touches
6 conflicts
0x9ef9caab…9c45
0x34b655…2a6f
6 touches
3 conflicts
0xb01fbce1…3de6
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity