pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,239,794
← previous block
next block →
recent activity
Analyzing
Block #93,239,794
11 transactions · 10 stateful · 2026-08-05 03:29:21 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,239,794
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x39435dac
· blocks 1
#4
0x5acec890
#5
0x5acec890
#6
updateDataFeedsValuesPartial
#7
executeBatch
#8
0x0f6795d9
· blocks 1
#9
setData
#3
0x39435dac
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x5fab7fbe…1ce5
0x34b655…2a6f
4 touches
1 conflict
0xb7fb89e5…b3c8
0x34b655…2a6f
4 touches
1 conflict
0xc88c0285…5372
0x34b655…2a6f
3 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
2 touches
0 conflicts
0x3782a203…e472
0x34b655…2a6f
2 touches
0 conflicts
0x39921786…0b17
0x34b655…2a6f
2 touches
0 conflicts
0x55898fed…c787
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:
Perpl
1 conflict on slot
0xbde524f475…b143bf
Audit this contract →
← previous block
·
next block →
recent activity