pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,025,566
← previous block
next block →
recent activity
Analyzing
Block #91,025,566
11 transactions · 10 stateful · 2026-07-28 09:46:29 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,025,566
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
delegate
#5
0x0f6795d9
· blocks 1
#6
0x3f5c179b
#8
0x6a687aec
#9
setData
#10
0x39435dac
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xa35509fa…5cb3
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1c91542b…f7b1
0x34b655…2a6f
2 touches
0 conflicts
0x20fbcaee…bb79
0x34b655…2a6f
2 touches
0 conflicts
0x301e1c77…9e30
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
0x34b655…2a6f
2 touches
0 conflicts
0x5e4b65e1…ebe1
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity