pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,468,149
← previous block
next block →
recent activity
Analyzing
Block #93,468,149
9 transactions · 8 stateful · 2026-08-05 22:37:28 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,468,149
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x39435dac
#3
0x5acec890
#4
0x0f6795d9
· blocks 2
#6
0x3f5c179b
#8
setData
#5
0x0f6795d9
· blocks 1
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb13b96bd…a3cb
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7c7eff13…16db
0x34b655…2a6f
4 touches
1 conflict
0x9b86aa76…6f62
0x34b655…2a6f
4 touches
1 conflict
0x0960ac51…5440
0x34b655…2a6f
4 touches
1 conflict
0x58620f29…db5a
0x34b655…2a6f
2 touches
0 conflicts
0x5e723ea2…9115
0x34b655…2a6f
2 touches
0 conflicts
0x691fa1b0…5b08
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
3 conflicts on slot
0xb13b96bd5b…77a3cb
Audit this contract →
← previous block
·
next block →
recent activity