← previous blocknext block →recent activity
Analyzing
Block #87,785,728
47 transactions · 33 stateful · 2026-07-14 22:02:48 UTC
Parallelism
60/100
Blocked
64%
Avg conflicts / tx
2.68
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #87,785,728 · 47 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
4w05w16w015w116w217w318w421w522w623w724w825w926w1027w1128w1229w1330w1435w241w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
28 touches
91 conflicts
0x9001f549…089d
0x34b655…2a6f
22 touches
55 conflicts
0xfb0022d6…1264
0x34b655…2a6f
20 touches
45 conflicts
0x5b145de0…367c
0xc8689a…ee79
20 touches
45 conflicts
0x28c62bca…b746
0x34b655…2a6f
20 touches
45 conflicts
0x9ae859db…2d84
0x34b655…2a6f
20 touches
45 conflicts
0x4c28eef3…fdab
0x34b655…2a6f
20 touches
45 conflicts
0x0dd44476…ef40
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
91 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity