← previous blocknext block →recent activity
Analyzing
Block #87,490,061
16 transactions · 13 stateful · 2026-07-13 13:04:22 UTC
Parallelism
63/100
Blocked
46%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,490,061 · 16 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
2w03w14w25w39w010w411w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x5b33f5b9…4bab
0x34b655…2a6f
10 touches
10 conflicts
0x0e8fecdb…7fe7
0x34b655…2a6f
8 touches
6 conflicts
0x26046442…e63a
0x34b655…2a6f
8 touches
6 conflicts
0x366c7d57…0ed1
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x01afed09…f19b
0x34b655…2a6f
8 touches
6 conflicts
0xec661a55…d9a1
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