pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,600,590
← previous block
next block →
recent activity
Analyzing
Block #100,600,590
10 transactions · 9 stateful · 2026-08-30 23:26:39 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,600,590
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x8263f5d9
#3
execOrders
#4
0x0c7abd22
· blocks 1
#6
updateDataFeedsValuesPartial
#7
execOrders
#8
batchUpdate
#9
execFwdPositionOpsV2
#5
execOrders
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
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x49028f08…fcc8
0x34b655…2a6f
3 touches
1 conflict
0xedd788b4…15ce
0x34b655…2a6f
3 touches
1 conflict
0x03cabc68…bc3b
0x34b655…2a6f
2 touches
0 conflicts
0x05086df1…bd5a
0x34b655…2a6f
2 touches
0 conflicts
0x07b538eb…09f8
0x34b655…2a6f
2 touches
0 conflicts
0x1bc17c3c…aa77
0x34b655…2a6f
2 touches
0 conflicts
0x2860b9bb…282c
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
0x7de579746e…f0f5ba
Audit this contract →
← previous block
·
next block →
recent activity