← previous blocknext block →recent activity
Analyzing
Block #87,913,316
19 transactions · 17 stateful · 2026-07-15 12:16:10 UTC
Parallelism
74/100
Blocked
53%
Avg conflicts / tx
1.11
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,913,316 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w09w110w213w314w415w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f6666e6…f280
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…000b
0x90c374…be45
10 touches
10 conflicts
0x4a870d86…79ef
0x336ed4…c59c
10 touches
10 conflicts
0x00000000…000a
0x90c374…be45
10 touches
10 conflicts
0x10a2bd5d…ad6d
0x8d1565…6723
10 touches
10 conflicts
0xc88f593e…5d93
0x336ed4…c59c
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x2eb48eb7…9d68
0x8d1565…6723
6 touches
3 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 0x0f6666e640…06f280
Audit this contract →
← previous block·next block →recent activity