pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,883,626
← previous block
next block →
recent activity
Analyzing
Block #99,883,626
15 transactions · 14 stateful · 2026-08-28 11:14:00 UTC
Parallelism
87
/100
Blocked
7
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,883,626
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#4
0x4cb2db39
· blocks 1
#6
forward
#7
execOrders
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
0xed82b078
#11
bet
#12
transferWithAuthorization
#13
setData
#14
execOrders
#5
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…000a
0x05a5a9…41ba
2 touches
0 conflicts
0x00000000…000b
0x05a5a9…41ba
2 touches
0 conflicts
0x00000000…000b
0x076d30…548c
2 touches
0 conflicts
0x00000000…0016
0x076d30…548c
2 touches
0 conflicts
0x12530975…a089
0x3bd359…433a
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:
0x80c74517…647210
1 conflict on slot
0x0000000000…00004c
Audit this contract →
← previous block
·
next block →
recent activity