← previous blocknext block →recent activity
Analyzing
Block #87,904,740
21 transactions · 19 stateful · 2026-07-15 11:18:48 UTC
Parallelism
76/100
Blocked
37%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,904,740 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w211w312w013w114w215w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xf79df061…e005
0xe52b14…7230
8 touches
6 conflicts
0xdfd64ea5…015c
0x34b655…2a6f
8 touches
6 conflicts
0x09a15b10…2639
0x754704…b603
8 touches
6 conflicts
0x5149ba0e…d954
0x754704…b603
8 touches
6 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
8 touches
6 conflicts
0x3845e7dc…c691
0xe52b14…7230
8 touches
6 conflicts
0x532023a5…d800
0xe52b14…7230
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity