← previous blocknext block →recent activity
Analyzing
Block #87,497,161
30 transactions · 25 stateful · 2026-07-13 13:51:53 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,497,161 · 30 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
10w012w116w217w018w120w221w324w425w427w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcfcb8911…e9da
0x34b655…2a6f
8 touches
6 conflicts
0x326d4924…1788
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0001
0xc1ff9f…b0fc
6 touches
3 conflicts
0x1c4970af…8823
0x34b655…2a6f
4 touches
1 conflict
0x2484cc15…5afc
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x50fb0834…d003
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0xcfcb891150…50e9da
Audit this contract →
← previous block·next block →recent activity