pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,682,611
← previous block
next block →
recent activity
Analyzing
Block #93,682,611
9 transactions · 9 stateful · 2026-08-06 16:35:35 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,682,611
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
#4
0x94defb17
· blocks 1
#6
0x0f6795d9
#7
0x6a74b84e
#8
setData
#5
0x94defb17
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
0xd3e01826…f3eb
0x968279…9342
4 touches
1 conflict
0x521a5982…a82a
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0xbaa882b1…537f
0x968279…9342
4 touches
1 conflict
0xbaa882b1…5380
0x968279…9342
4 touches
1 conflict
0xbaa882b1…5382
0x968279…9342
4 touches
1 conflict
0xd3e01826…f3e5
0x968279…9342
4 touches
1 conflict
0xd3e01826…f3e6
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
0xd3e01826d9…9bf3eb
Audit this contract →
← previous block
·
next block →
recent activity