pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,536,632
← previous block
next block →
recent activity
Analyzing
Block #92,536,632
11 transactions · 10 stateful · 2026-08-02 16:29:48 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,536,632
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execFwdPositionOps
#3
execFwdPositionOps
#4
0x3f5c179b
#5
0x94defb17
· blocks 1
#7
setData
#8
execOrders
#9
execOrders
#10
0x59558d29
#6
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa559a9f0…e521
0x968279…9342
4 touches
1 conflict
0x45a4eee7…6245
0x968279…9342
4 touches
1 conflict
0x45a4eee7…6246
0x968279…9342
4 touches
1 conflict
0x45a4eee7…6247
0x968279…9342
4 touches
1 conflict
0x45a4eee7…6248
0x968279…9342
4 touches
1 conflict
0xa559a9f0…e51b
0x968279…9342
4 touches
1 conflict
0xa559a9f0…e51c
0x968279…9342
4 touches
1 conflict
0xa559a9f0…e51f
0x968279…9342
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:
0x96827978…f09342
1 conflict on slot
0xa559a9f00e…d4e521
Audit this contract →
← previous block
·
next block →
recent activity