pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,572,581
← previous block
next block →
recent activity
Analyzing
Block #93,572,581
10 transactions · 9 stateful · 2026-08-06 07:22:26 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,572,581
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
0x0f6795d9
· blocks 1
#3
handleOps
#5
updateDataFeedsValuesPartial
#6
updateTemporalNumericValuesV1
#7
0x6a7436aa
#8
transfer
#9
setData
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe9273dc5…efb4
0x34b655…2a6f
4 touches
1 conflict
0x393a6e65…e8a2
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x0dd3d3cd…7281
0x34b655…2a6f
2 touches
0 conflicts
0x0dff61c6…b97a
0x34b655…2a6f
2 touches
0 conflicts
0x0fc81850…e472
0x34b655…2a6f
2 touches
0 conflicts
0x1691317e…7f1e
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
0xe9273dc526…adefb4
Audit this contract →
← previous block
·
next block →
recent activity