← previous blocknext block →recent activity
Analyzing
Block #87,315,911
20 transactions · 18 stateful · 2026-07-12 17:39:47 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,315,911 · 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
2w05w16w07w18w29w310w411w512w013w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf83843c9…7068
0xe52b14…7230
12 touches
15 conflicts
0x09a15b10…2639
0x754704…b603
12 touches
15 conflicts
0x5149ba0e…d954
0x754704…b603
12 touches
15 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
12 touches
15 conflicts
0x3845e7dc…c691
0xe52b14…7230
12 touches
15 conflicts
0x532023a5…d800
0xe52b14…7230
12 touches
15 conflicts
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0x7fea9a79…6655
0xe52b14…7230
10 touches
15 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: 0xe52b1424…bb7230
15 conflicts on slot 0xf83843c9b9…a57068
Audit this contract →
← previous block·next block →recent activity