pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,064,356
← previous block
next block →
recent activity
Analyzing
Block #93,064,356
8 transactions · 7 stateful · 2026-08-04 12:45:58 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,064,356
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x94defb17
· blocks 1
#4
0x0f6795d9
#5
updateDataFeedsValuesPartial
#6
0x6a71df7e
#7
setData
#3
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bbfe796…637f
0x968279…9342
4 touches
1 conflict
0x2bbfe796…6382
0x968279…9342
4 touches
1 conflict
0x2bbfe796…6383
0x968279…9342
4 touches
1 conflict
0x2bbfe796…6385
0x968279…9342
4 touches
1 conflict
0xfd6ed6f2…8167
0x968279…9342
4 touches
1 conflict
0xfd6ed6f2…8168
0x968279…9342
4 touches
1 conflict
0xfd6ed6f2…816a
0x968279…9342
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
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
0x2bbfe796e6…ab637f
Audit this contract →
← previous block
·
next block →
recent activity