pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,049,075
← previous block
next block →
recent activity
Analyzing
Block #102,049,075
11 transactions · 10 stateful · 2026-09-05 01:00:29 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,049,075
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x00e01c…fbac
#3
execOrders
· blocks 1
#5
0xab083028
#6
execOrders
#7
updateDataFeedsValuesPartial
#8
setData
#9
execFwdPositionOpsV2
#10
0x6a9b69af
#4
execOrders
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
0xddf10453…d774
0x34b655…2a6f
4 touches
1 conflict
0x1d821a69…b822
0x34b655…2a6f
4 touches
1 conflict
0x3f60bfe7…b05d
0x34b655…2a6f
4 touches
1 conflict
0x463e1e6b…87b5
0x34b655…2a6f
4 touches
1 conflict
0x53e08444…d671
0x34b655…2a6f
4 touches
1 conflict
0x67043b0b…97d7
0x34b655…2a6f
4 touches
1 conflict
0x7e273bc0…5dbc
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
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
0xddf10453a0…20d774
Audit this contract →
← previous block
·
next block →
recent activity