pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,921,696
← previous block
next block →
recent activity
Analyzing
Block #93,921,696
13 transactions · 9 stateful · 2026-08-07 12:38:00 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,921,696
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execOrder
· blocks 1
#3
0x41a8f47c
#4
updateDataFeedsValuesPartial
#5
execOrders
#6
aggregate3
#7
batchUpdate
#9
0x6a75d220
#10
setData
#11
0xcfe9ce…e2c0
#12
0x750151…24ea
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6636a104…d595
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xee6a7813…f73d
0x34b655…2a6f
4 touches
1 conflict
0x7b6fc061…71cf
0x065c9d…c394
2 touches
0 conflicts
0xd7616f56…4439
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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
0x6636a1041f…2dd595
Audit this contract →
← previous block
·
next block →
recent activity