pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,996,189
← previous block
next block →
recent activity
Analyzing
Block #91,996,189
11 transactions · 11 stateful · 2026-07-31 19:11:46 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,996,189
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 1
#4
forward
#5
0x0f6795d9
#6
0x6a6cf3e9
#7
setData
#8
0x39435dac
#9
0x59558d29
#10
0xc7e3ec2c
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x04994ed2…9032
0x34b655…2a6f
2 touches
0 conflicts
0x0af50e38…ba88
0x34b655…2a6f
2 touches
0 conflicts
0x103a0980…30c8
0x34b655…2a6f
2 touches
0 conflicts
0x1eb410fd…591d
0x34b655…2a6f
2 touches
0 conflicts
0x35725c97…85b4
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity