pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,697,200
← previous block
next block →
recent activity
Analyzing
Block #92,697,200
10 transactions · 10 stateful · 2026-08-03 05:58:18 UTC
Parallelism
60
/100
Blocked
30
%
Avg conflicts / tx
0.4
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,697,200
· 10 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
execOrder
· blocks 2
#2
0x3f5c179b
#4
0x6df9e92b
#5
setData
#8
0x59558d29
#9
0xc7e3ec2c
#3
execFwdPositionOps
· blocks 1
#6
execOrders
· blocks 1
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
6
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc49be57b…2a7a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x746bcce3…d0ce
0x34b655…2a6f
4 touches
1 conflict
0xb6864dd7…0df8
0x34b655…2a6f
4 touches
1 conflict
0x7a2fc410…c088
0x34b655…2a6f
4 touches
1 conflict
0x85971f5d…e920
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity