pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,065,006
← previous block
next block →
recent activity
Analyzing
Block #98,065,006
14 transactions · 6 stateful · 2026-08-22 01:45:18 UTC
Parallelism
86
/100
Blocked
17
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,065,006
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
#2
0x41a8f47c
#3
0x41a8f47c
#4
execOrders
#5
0x59558d29
#6
execPerpOps
#7
0x0c7abd22
#8
0x0c7abd22
#9
setData
· blocks 1
#11
execOrders
#12
execOrders
#13
0x7b84f330
#10
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1fd77335…9120
0x34b655…2a6f
2 touches
0 conflicts
0x316a7140…e39a
0x34b655…2a6f
2 touches
0 conflicts
0x522e20b4…fbc4
0x34b655…2a6f
2 touches
0 conflicts
0x58620f29…db5a
0x34b655…2a6f
2 touches
0 conflicts
0x72230ed6…071b
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:
0x33176be2…ede078
1 conflict on slot
0x09106a952c…111467
Audit this contract →
← previous block
·
next block →
recent activity