← previous blocknext block →recent activity
Analyzing
Block #87,356,036
38 transactions · 33 stateful · 2026-07-12 22:08:05 UTC
Parallelism
66/100
Blocked
67%
Avg conflicts / tx
2.21
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,356,036 · 38 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
1w02w15w26w27w38w39w010w113w014w115w216w317w418w519w620w721w824w227w829w930w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xaa2a27f2…d53b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xdb3937e8…23cb
0x34b655…2a6f
8 touches
6 conflicts
0x01f1fdd6…d791
0xd32edf…ff58
7 touches
6 conflicts
0x83fcbad4…dadd
0x34b655…2a6f
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
36 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity