← previous blocknext block →recent activity
Analyzing
Block #87,704,628
86 transactions · 62 stateful · 2026-07-14 13:00:04 UTC
Parallelism
74/100
Blocked
76%
Avg conflicts / tx
2.85
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #87,704,628 · 86 txs across 22 waves · depth 22
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
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w113w016w119w222w323w461w362w572w173w474w575w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
30 touches
105 conflicts
0xac2a0273…721b
0x34b655…2a6f
20 touches
45 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
18 touches
36 conflicts
0x7fd53511…8f76
0x34b655…2a6f
18 touches
36 conflicts
0xa57576bb…e01f
0x34b655…2a6f
16 touches
28 conflicts
0xad09dd03…27d0
0x34b655…2a6f
16 touches
28 conflicts
0xce40a269…92eb
0x34b655…2a6f
16 touches
28 conflicts
0x767799cd…f423
0xc8689a…ee79
16 touches
28 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
105 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity