← previous blocknext block →recent activity
Analyzing
Block #87,748,825
33 transactions · 27 stateful · 2026-07-14 17:55:55 UTC
Parallelism
61/100
Blocked
59%
Avg conflicts / tx
2.15
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,748,825 · 33 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w09w110w211w312w413w514w615w716w823w928w1032w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9001f549…089d
0x34b655…2a6f
22 touches
55 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0xfa6e44cf…eda0
0x34b655…2a6f
16 touches
28 conflicts
0x22e7ebfe…1293
0x34b655…2a6f
16 touches
28 conflicts
0x5b145de0…367c
0xc8689a…ee79
16 touches
28 conflicts
0x4755fafb…859b
0x34b655…2a6f
16 touches
28 conflicts
0x58620f29…db5a
0x34b655…2a6f
16 touches
28 conflicts
0x402f7978…164c
0x34b655…2a6f
10 touches
10 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
55 conflicts on slot 0x9001f5497d…54089d
Audit this contract →
← previous block·next block →recent activity