pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,065,903
← previous block
next block →
recent activity
Analyzing
Block #98,065,903
13 transactions · 12 stateful · 2026-08-22 01:49:49 UTC
Parallelism
85
/100
Blocked
17
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,065,903
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
· blocks 1
#2
execute
#3
0x6ad2e98b
#4
execOrders
· blocks 1
#5
0xb2d4797b
#6
0x59558d29
#7
execOrder
#9
0x3f5c179b
#10
0xed82b078
#11
setData
#8
execFwdPositionOpsV2
#12
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
8
w1
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xead15497…1dbe
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x729c91b8…9537
0x188d58…ea8e
2 touches
0 conflicts
0x729c91b8…9539
0x188d58…ea8e
2 touches
0 conflicts
0xd8fd2add…50fc
0x2b46c0…1669
2 touches
0 conflicts
0x005321e0…2e05
0x34b655…2a6f
2 touches
0 conflicts
0x09b7cda2…2312
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
0xead15497a3…971dbe
Audit this contract →
← previous block
·
next block →
recent activity