pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,813,691
← previous block
next block →
recent activity
Analyzing
Block #99,813,691
8 transactions · 7 stateful · 2026-08-28 05:20:47 UTC
Parallelism
50
/100
Blocked
43
%
Avg conflicts / tx
0.38
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,813,691
· 8 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
execOrders
· blocks 1
#3
setData
#4
0x3f5c179b
#5
execFwdPositionOpsV2
#2
execOrders
· 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
2
w1
6
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x15698ac9…2a46
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x076b9edf…e35c
0x34b655…2a6f
2 touches
0 conflicts
0x258fcaf5…2084
0x34b655…2a6f
2 touches
0 conflicts
0x375658d5…5e5f
0x34b655…2a6f
2 touches
0 conflicts
0x3952b40f…4c8c
0x34b655…2a6f
2 touches
0 conflicts
0x41bb8a33…9346
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
0x15698ac9db…df2a46
Audit this contract →
← previous block
·
next block →
recent activity