← previous blocknext block →recent activity
Analyzing
Block #87,643,611
23 transactions · 19 stateful · 2026-07-14 06:12:04 UTC
Parallelism
74/100
Blocked
42%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,643,611 · 23 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
1w02w110w011w212w113w215w316w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x435b08b5…d84e
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x7e5ea60a…c4a4
0x34b655…2a6f
6 touches
3 conflicts
0x73099353…383c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x0181bb37…6628
0x34b655…2a6f
6 touches
3 conflicts
0x4f4a7ac3…021c
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 0x435b08b54c…2bd84e
Audit this contract →
← previous block·next block →recent activity