pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,798,363
← previous block
next block →
recent activity
Analyzing
Block #101,798,363
14 transactions · 13 stateful · 2026-09-04 03:53:05 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,798,363
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
execOrder
#3
0x5acec890
· blocks 1
#5
0x5acec890
#6
execOrders
#7
0x59558d29
#8
0x59558d29
#9
setData
#10
buy
#11
execFwdPositionOpsV2
#12
0x6a9a4119
#13
execOrders
#4
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x02f34478…0ca1
0x34b655…2a6f
2 touches
0 conflicts
0x03da5c00…b353
0x34b655…2a6f
2 touches
0 conflicts
0x337ba70b…6c22
0x34b655…2a6f
2 touches
0 conflicts
0x366a19b0…f065
0x34b655…2a6f
2 touches
0 conflicts
0x3f152ba8…cea6
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
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity