← previous blocknext block →recent activity
Analyzing
Block #87,718,860
40 transactions · 34 stateful · 2026-07-14 14:35:28 UTC
Parallelism
70/100
Blocked
76%
Avg conflicts / tx
2.48
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #87,718,860 · 40 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w08w19w010w115w116w217w323w324w425w626w227w129w733w235w437w938w10
- 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
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0xa0b17484…2b19
0x34b655…2a6f
8 touches
6 conflicts
0xef7cdebf…b33b
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity