pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,345,326
← previous block
next block →
recent activity
Analyzing
Block #93,345,326
10 transactions · 8 stateful · 2026-08-05 12:19:57 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,345,326
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 2
#2
forward
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x6a732ae4
#7
setData
#8
0x9d0c28…a1b7
#3
0x0f6795d9
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8fe37a3f…4c89
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfed09e59…a493
0x34b655…2a6f
4 touches
1 conflict
0x03695af7…8944
0x34b655…2a6f
2 touches
0 conflicts
0x1569336c…65e2
0x34b655…2a6f
2 touches
0 conflicts
0x1bee5aea…5f61
0x34b655…2a6f
2 touches
0 conflicts
0x237fbe48…657b
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
0x8fe37a3f4a…bf4c89
Audit this contract →
← previous block
·
next block →
recent activity