← previous blocknext block →recent activity
Analyzing
Block #87,489,974
18 transactions · 18 stateful · 2026-07-13 13:03:48 UTC
Parallelism
72/100
Blocked
50%
Avg conflicts / tx
1.06
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,489,974 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w36w47w08w110w211w316w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x521f03f8…dc0e
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x9f7a24c2…7b3c
0x34b655…2a6f
8 touches
6 conflicts
0xc66dd2b5…970d
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xa1002523…644f
0x34b655…2a6f
6 touches
3 conflicts
0xad0c7701…1d83
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 0x521f03f844…eedc0e
Audit this contract →
← previous block·next block →recent activity