← previous blocknext block →recent activity
Analyzing
Block #86,977,540
16 transactions · 14 stateful · 2026-07-11 03:57:30 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,977,540 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
14w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc4e5eab…639b
0x34b655…2a6f
4 touches
1 conflict
0x74888025…a5b8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x17c3727d…cb0e
0x34b655…2a6f
2 touches
0 conflicts
0x1a28e34b…1404
0x34b655…2a6f
2 touches
0 conflicts
0x22bc4ea4…5c8a
0x34b655…2a6f
2 touches
0 conflicts
0x286711a5…b3bf
0x34b655…2a6f
2 touches
0 conflicts
0x342cf4de…0a48
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xfc4e5eab2e…12639b
Audit this contract →
← previous block·next block →recent activity