← previous blocknext block →recent activity
Analyzing
Block #87,487,898
26 transactions · 19 stateful · 2026-07-13 12:49:54 UTC
Parallelism
81/100
Blocked
42%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,487,898 · 26 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
1w06w07w08w111w012w115w217w018w319w420w221w123w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c04ce68…d007
0x34b655…2a6f
6 touches
3 conflicts
0xc3688185…9b36
0x34b655…2a6f
6 touches
3 conflicts
0x28f13cc4…7ecf
0xd32edf…ff58
5 touches
3 conflicts
0x231711a0…4ebd
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0x3a6290da…e683
0x34b655…2a6f
4 touches
1 conflict
0x624f5270…c75d
0x34b655…2a6f
4 touches
1 conflict
0x628912e6…e316
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
3 conflicts on slot 0x4c04ce6804…bbd007
Audit this contract →
← previous block·next block →recent activity