← previous blocknext block →recent activity
Analyzing
Block #87,078,539
17 transactions · 16 stateful · 2026-07-11 15:12:09 UTC
Parallelism
76/100
Blocked
31%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,078,539 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w18w011w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde30d77…b032
0x34b655…2a6f
8 touches
6 conflicts
0x16363afe…d410
0x34b655…2a6f
4 touches
1 conflict
0x1a28e34b…1404
0x34b655…2a6f
4 touches
1 conflict
0x286711a5…b3bf
0x34b655…2a6f
4 touches
1 conflict
0x2c390858…b1ed
0x34b655…2a6f
4 touches
1 conflict
0x482f3ed7…3307
0x34b655…2a6f
4 touches
1 conflict
0x482f3ed7…3308
0x34b655…2a6f
4 touches
1 conflict
0x49baada3…357f
0x34b655…2a6f
4 touches
1 conflict
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 0xbde30d77ef…1cb032
Audit this contract →
← previous block·next block →recent activity