← previous blocknext block →recent activity
Analyzing
Block #87,703,827
40 transactions · 29 stateful · 2026-07-14 12:54:41 UTC
Parallelism
68/100
Blocked
66%
Avg conflicts / tx
2.1
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,703,827 · 40 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
1w04w16w211w012w117w018w119w220w321w422w523w624w725w826w927w1030w1131w233w238w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x21605a79…d719
0x34b655…2a6f
8 touches
6 conflicts
0x258fcaf5…2084
0x34b655…2a6f
6 touches
3 conflicts
0x74a7b40b…8922
0x34b655…2a6f
6 touches
3 conflicts
0x7fd53511…8f76
0x34b655…2a6f
6 touches
3 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
6 touches
3 conflicts
0x95c47f03…f1bb
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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity