pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,236,534
← previous block
next block →
recent activity
Analyzing
Block #93,236,534
9 transactions · 9 stateful · 2026-08-05 03:12:58 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,236,534
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x5acec890
#3
0x5acec890
· blocks 2
#6
execFwdPositionOps
#7
setData
#8
execOrders
#4
0x5acec890
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd96e7dd9…4550
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x1eb0fab5…3517
0x34b655…2a6f
2 touches
0 conflicts
0x282f129e…8f33
0x34b655…2a6f
2 touches
0 conflicts
0x2999ebda…ce6c
0x34b655…2a6f
2 touches
0 conflicts
0x37d710c8…45c1
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
0xd96e7dd95c…f34550
Audit this contract →
← previous block
·
next block →
recent activity