← previous blocknext block →recent activity
Analyzing
Block #87,409,153
39 transactions · 34 stateful · 2026-07-13 04:03:23 UTC
Parallelism
64/100
Blocked
65%
Avg conflicts / tx
1.67
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,409,153 · 39 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w011w112w213w014w115w216w017w118w219w122w324w427w233w934w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc514314c…1aa4
0x34b655…2a6f
8 touches
6 conflicts
0xc08384da…ecb7
0x34b655…2a6f
8 touches
6 conflicts
0x734ee320…caae
0x34b655…2a6f
8 touches
6 conflicts
0x3fc40870…7ef4
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity