pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,132,498
← previous block
next block →
recent activity
Analyzing
Block #91,132,498
10 transactions · 10 stateful · 2026-07-28 18:44:31 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,132,498
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
executeBatch
#2
0x0f6795d9
#3
0x0f6795d9
#4
updateDataFeedsValuesPartial
#5
0x39435dac
· blocks 2
#8
0x6a68f906
#9
setData
#6
0x39435dac
· blocks 1
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x4bc1abab…5874
0x34b655…2a6f
6 touches
3 conflicts
0x3ac06bf5…9424
0x34b655…2a6f
4 touches
1 conflict
0xad6d718a…7b7a
0x34b655…2a6f
4 touches
1 conflict
0x7c4b1eee…975a
0x34b655…2a6f
3 touches
1 conflict
0x58733c38…f2cd
0xe52b14…7230
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
0xf3d10975b0…050d07
Audit this contract →
← previous block
·
next block →
recent activity