← previous blocknext block →recent activity
Analyzing
Block #87,498,650
19 transactions · 19 stateful · 2026-07-13 14:01:51 UTC
Parallelism
68/100
Blocked
32%
Avg conflicts / tx
0.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,498,650 · 19 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
3w04w05w16w18w29w312w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe20a9313…c20a
0x34b655…2a6f
8 touches
6 conflicts
0x8cf1f868…c5af
0x34b655…2a6f
6 touches
3 conflicts
0x2a90bc5b…4a86
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x35075a55…56b4
0x34b655…2a6f
4 touches
1 conflict
0x363a4317…87d2
0x34b655…2a6f
4 touches
1 conflict
0x366c7d57…0ed1
0x34b655…2a6f
4 touches
1 conflict
0x388633a0…86cd
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 0xe20a9313bb…13c20a
Audit this contract →
← previous block·next block →recent activity