pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,502,753
← previous block
next block →
recent activity
Analyzing
Block #97,502,753
8 transactions · 8 stateful · 2026-08-20 02:09:00 UTC
Parallelism
50
/100
Blocked
50
%
Avg conflicts / tx
0.75
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,502,753
· 8 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
execOrders
· blocks 2
#2
0xab083028
#7
0x3f5c179b
#3
execOrder
· blocks 2
#4
execOrder
· blocks 1
#5
execOrder
· blocks 1
#6
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
5
w2
6
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x886f7fe6…8b7a
0x34b655…2a6f
6 touches
3 conflicts
0xa21e8abe…a7f1
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x35782921…6a45
0x34b655…2a6f
4 touches
1 conflict
0xd9f0f90b…741a
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x94710b77…a921
0x34b655…2a6f
4 touches
1 conflict
0xee75c266…f8c6
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
3 conflicts on slot
0x886f7fe654…c88b7a
Audit this contract →
← previous block
·
next block →
recent activity