pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,554,295
← previous block
next block →
recent activity
Analyzing
Block #95,554,295
11 transactions · 9 stateful · 2026-08-13 06:01:26 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,554,295
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
execOrders
#3
0x5acec890
#4
updateDataFeedsValuesPartial
#5
handleOps
· blocks 1
#7
0x94defb17
#8
batchUpdate
#9
setData
#10
0x59558d29
#6
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33a26eb2…2df0
0x5ff137…2789
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x007c19a0…3af4
0x34b655…2a6f
2 touches
0 conflicts
0x00ddbbf2…4588
0x34b655…2a6f
2 touches
0 conflicts
0x0a51d6fa…1ea1
0x34b655…2a6f
2 touches
0 conflicts
0x4bc1abab…5874
0x34b655…2a6f
2 touches
0 conflicts
0x7f5b2c1d…0e7f
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:
0x5ff137d4…6d2789
1 conflict on slot
0x33a26eb216…ad2df0
Audit this contract →
← previous block
·
next block →
recent activity