pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,079,296
← previous block
next block →
recent activity
Analyzing
Block #98,079,296
9 transactions · 9 stateful · 2026-08-22 02:57:13 UTC
Parallelism
56
/100
Blocked
44
%
Avg conflicts / tx
0.78
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,079,296
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0xab083028
· blocks 1
#3
forward
#4
transferWithAuthorization
· blocks 3
#8
setData
#2
batchUpdate
#5
transferWithAuthorization
· blocks 2
#6
transferWithAuthorization
· blocks 1
#7
transferWithAuthorization
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
6
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
2 touches
0 conflicts
0x6518075e…2b17
0x2a68ba…90c5
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x065ff70b…356d
0x40c49f…2af0
2 touches
0 conflicts
0x3f81bcfb…2905
0x40c49f…2af0
2 touches
0 conflicts
0x63887737…bd6b
0x40c49f…2af0
2 touches
0 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:
USDC (USDC)
6 conflicts on slot
0xd17580f913…78ece1
Audit this contract →
← previous block
·
next block →
recent activity