← previous blocknext block →recent activity
Analyzing
Block #87,418,738
19 transactions · 15 stateful · 2026-07-13 05:07:31 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,418,738 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w29w310w011w112w216w217w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xdef5089b…6861
0x0a2fbf…29b1
6 touches
3 conflicts
0xdef5089b…6862
0x0a2fbf…29b1
6 touches
3 conflicts
0xdef5089b…6865
0x0a2fbf…29b1
6 touches
3 conflicts
0x00000000…0006
0x0a2fbf…29b1
6 touches
3 conflicts
0x310ce8a5…2e0d
0x0a2fbf…29b1
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
6 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity