pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,527,804
← previous block
next block →
recent activity
Analyzing
Block #98,527,804
8 transactions · 8 stateful · 2026-08-23 16:40:19 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,527,804
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
execOrders
· blocks 1
#4
0x59558d29
#5
execFwdPositionOpsV2
#6
0x6a8b22eb
#7
setData
#3
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x052887af…89a3
0x34b655…2a6f
2 touches
0 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
2 touches
0 conflicts
0x0cb06a1e…b6fa
0x34b655…2a6f
2 touches
0 conflicts
0x1408e7c7…f324
0x34b655…2a6f
2 touches
0 conflicts
0x1d7bbd81…7cc6
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
0xbde524f475…b143bf
Audit this contract →
← previous block
·
next block →
recent activity