pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,205,295
← previous block
next block →
recent activity
Analyzing
Block #94,205,295
12 transactions · 10 stateful · 2026-08-08 12:27:52 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,205,295
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
#3
execOrders
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
0x94defb17
· blocks 1
#8
0xed82b078
#9
execFwdPositionOps
#10
setData
#11
execOrders
#7
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6ea7305…180c
0x968279…9342
4 touches
1 conflict
0x521a5982…a82a
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0x5541588c…add2
0x968279…9342
4 touches
1 conflict
0x5541588c…add3
0x968279…9342
4 touches
1 conflict
0x5541588c…add6
0x968279…9342
4 touches
1 conflict
0x5541588c…add7
0x968279…9342
4 touches
1 conflict
0x5541588c…add9
0x968279…9342
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:
0x96827978…f09342
1 conflict on slot
0xc6ea730501…0f180c
Audit this contract →
← previous block
·
next block →
recent activity