pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,810,383
← previous block
next block →
recent activity
Analyzing
Block #91,810,383
11 transactions · 9 stateful · 2026-07-31 03:37:01 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,810,383
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
#2
0x0f6795d9
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
#5
0x39435dac
#6
0x6a6c18d5
#7
setData
#8
0x39435dac
· blocks 1
#10
0x59558d29
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x032128e1…4edf
0x34b655…2a6f
4 touches
1 conflict
0x00966e54…7d1d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdc8d4ee0…def3
0x34b655…2a6f
4 touches
1 conflict
0xe85638e6…207a
0x34b655…2a6f
4 touches
1 conflict
0x3111a64f…eb7f
0x34b655…2a6f
2 touches
0 conflicts
0x3932086f…b68b
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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
0x032128e140…cd4edf
Audit this contract →
← previous block
·
next block →
recent activity