← previous blocknext block →recent activity
Analyzing
Block #87,918,783
47 transactions · 34 stateful · 2026-07-15 12:52:43 UTC
Parallelism
72/100
Blocked
74%
Avg conflicts / tx
1.77
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,918,783 · 47 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w27w08w112w013w116w017w121w122w223w330w532w733w134w335w436w537w240w741w842w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x546671c8…080a
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x56b5f5c0…a3ad
0x34b655…2a6f
8 touches
6 conflicts
0x53699236…fede
0x34b655…2a6f
8 touches
6 conflicts
0x66a11a3b…0ee9
0xa6afd3…d132
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity