pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,352,098
← previous block
next block →
recent activity
Analyzing
Block #93,352,098
8 transactions · 8 stateful · 2026-08-05 12:53:59 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,352,098
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 2
#4
0x3f5c179b
#5
0x0f6795d9
#6
setData
#7
0x59558d29
#2
0x0f6795d9
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x772ab420…c2f6
0x34b655…2a6f
4 touches
1 conflict
0xfed09e59…a493
0x34b655…2a6f
4 touches
1 conflict
0x0189810e…848a
0x34b655…2a6f
2 touches
0 conflicts
0x09790557…7c26
0x34b655…2a6f
2 touches
0 conflicts
0x0cdc38ed…c280
0x34b655…2a6f
2 touches
0 conflicts
0x268fe2a8…1d82
0x34b655…2a6f
2 touches
0 conflicts
0x28225554…5bde
0x34b655…2a6f
2 touches
0 conflicts
0x2c192519…3e3b
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
0x772ab420dc…dcc2f6
Audit this contract →
← previous block
·
next block →
recent activity