← previous blocknext block →recent activity
Analyzing
Block #87,592,485
54 transactions · 44 stateful · 2026-07-14 00:30:13 UTC
Parallelism
65/100
Blocked
82%
Avg conflicts / tx
3.3
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #87,592,485 · 54 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w36w49w010w136w539w640w741w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
26 touches
78 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
18 touches
36 conflicts
0x1de49243…4aa3
0x34b655…2a6f
16 touches
28 conflicts
0x2d8a87f4…9991
0x34b655…2a6f
16 touches
28 conflicts
0x5e3a31d1…7a6e
0x34b655…2a6f
16 touches
28 conflicts
0x5b145de0…367c
0xc8689a…ee79
16 touches
28 conflicts
0x1750da27…5388
0x34b655…2a6f
16 touches
28 conflicts
0x8d4a873e…1ada
0x34b655…2a6f
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
78 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity