← previous blocknext block →recent activity
Analyzing
Block #87,760,531
19 transactions · 17 stateful · 2026-07-14 19:14:11 UTC
Parallelism
63/100
Blocked
41%
Avg conflicts / tx
1.16
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,760,531 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w49w510w611w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28c62bca…b746
0x34b655…2a6f
14 touches
21 conflicts
0x5b145de0…367c
0xc8689a…ee79
14 touches
21 conflicts
0xaa643d44…2122
0x34b655…2a6f
14 touches
21 conflicts
0x9ae859db…2d84
0x34b655…2a6f
14 touches
21 conflicts
0x9001f549…089d
0x34b655…2a6f
14 touches
21 conflicts
0x747f609d…1555
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x262f4188…0178
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
21 conflicts on slot 0x28c62bca1a…d4b746
Audit this contract →
← previous block·next block →recent activity