← previous blocknext block →recent activity
Analyzing
Block #87,623,200
19 transactions · 16 stateful · 2026-07-14 03:55:36 UTC
Parallelism
63/100
Blocked
56%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,623,200 · 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
4w05w16w27w38w410w111w114w217w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xa0fc0efb…23b1
0x34b655…2a6f
10 touches
10 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
10 touches
10 conflicts
0x53bddbe8…2e5e
0x34b655…2a6f
8 touches
6 conflicts
0xed59b1cd…8509
0x34b655…2a6f
8 touches
6 conflicts
0xd19c9d38…b459
0x34b655…2a6f
8 touches
6 conflicts
0xd11dcf4e…518f
0x34b655…2a6f
8 touches
6 conflicts
0xb59b0c85…f36c
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity