pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,543,868
← previous block
next block →
recent activity
Analyzing
Block #91,543,868
10 transactions · 9 stateful · 2026-07-30 05:16:21 UTC
Parallelism
70
/100
Blocked
33
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,543,868
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x6ad2e98b
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
· blocks 1
#6
0x0f6795d9
#8
setData
#2
0x0c7abd22
#7
0x0f6795d9
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
7
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c143362…7154
0x34b655…2a6f
4 touches
1 conflict
0x707decdf…dc33
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x849c2133…33c6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
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
0x6c14336297…a27154
Audit this contract →
← previous block
·
next block →
recent activity