← previous blocknext block →recent activity
Analyzing
Block #87,710,136
58 transactions · 35 stateful · 2026-07-14 13:36:56 UTC
Parallelism
71/100
Blocked
69%
Avg conflicts / tx
1.83
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,710,136 · 58 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w314w028w029w130w231w332w433w534w635w736w837w941w1043w1244w1347w348w449w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0xa558e115…fc88
0x34b655…2a6f
10 touches
10 conflicts
0x8fe37a3f…4c89
0x34b655…2a6f
10 touches
10 conflicts
0xe3321cb6…26de
0x34b655…2a6f
8 touches
6 conflicts
0xd958a1dd…705d
0x34b655…2a6f
8 touches
6 conflicts
0xc03846bb…73b3
0x34b655…2a6f
8 touches
6 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
8 touches
6 conflicts
0x197e2da8…f1f4
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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity