pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,079,812
← previous block
next block →
recent activity
Analyzing
Block #98,079,812
15 transactions · 12 stateful · 2026-08-22 02:59:49 UTC
Parallelism
87
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,079,812
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x7b84f330
#3
execOrders
#4
execOrders
· blocks 1
#5
0x59558d29
#6
0x5acec890
#7
0x3f5c179b
#8
forward
#9
forward
#10
forward
#12
setData
#13
0x61d59c2d
#14
0x7b84f330
#11
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81716ce9…095f
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x000bde1a…e123
0x34b655…2a6f
2 touches
0 conflicts
0x0323ea1a…00b0
0x34b655…2a6f
2 touches
0 conflicts
0x2860b9bb…282c
0x34b655…2a6f
2 touches
0 conflicts
0x299e547d…af09
0x34b655…2a6f
2 touches
0 conflicts
0x2c001e45…d749
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0x81716ce924…61095f
Audit this contract →
← previous block
·
next block →
recent activity