← previous blocknext block →recent activity
Analyzing
Block #87,690,877
20 transactions · 18 stateful · 2026-07-14 11:27:53 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,690,877 · 20 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
2w04w05w17w28w09w310w412w113w014w515w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4a4
0x34b655…2a6f
8 touches
6 conflicts
0x8d515c9b…bc1a
0x34b655…2a6f
8 touches
6 conflicts
0x0dfafef1…5c2e
0x34b655…2a6f
6 touches
3 conflicts
0x36b8bd62…0beb
0x34b655…2a6f
6 touches
3 conflicts
0x378c030c…a8a4
0x34b655…2a6f
6 touches
3 conflicts
0x4620ab0b…e468
0x34b655…2a6f
6 touches
3 conflicts
0x53f393fa…00b9
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
6 conflicts on slot 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity