← previous blocknext block →recent activity
Analyzing
Block #87,727,507
35 transactions · 31 stateful · 2026-07-14 15:33:19 UTC
Parallelism
57/100
Blocked
61%
Avg conflicts / tx
2.46
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,727,507 · 35 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w010w211w312w413w514w615w716w817w918w1019w1122w1123w1224w1229w132w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0xafb8e71e…9285
0x34b655…2a6f
10 touches
10 conflicts
0x2b7950c1…2342
0x34b655…2a6f
10 touches
10 conflicts
0xa9f59232…f58c
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x727b1b1a…e403
0x34b655…2a6f
8 touches
6 conflicts
0x7a12cccc…57f8
0x34b655…2a6f
8 touches
6 conflicts
0x92b49f44…ee4f
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
45 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity