← previous blocknext block →recent activity
Analyzing
Block #87,582,799
17 transactions · 14 stateful · 2026-07-13 23:25:27 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,582,799 · 17 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
3w05w16w27w18w310w411w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d2f0b01…112a
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xb4ca3e09…e96b
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x1b89bfcf…8506
0x34b655…2a6f
4 touches
1 conflict
0x44b80fe8…bfa7
0x34b655…2a6f
4 touches
1 conflict
0x63241156…6343
0x34b655…2a6f
4 touches
1 conflict
0x76c4d722…afa9
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 0x5d2f0b01fb…19112a
Audit this contract →
← previous block·next block →recent activity