pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,983,114
← previous block
next block →
recent activity
Analyzing
Block #91,983,114
11 transactions · 8 stateful · 2026-07-31 18:06:00 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,983,114
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x4d8dc985
#3
0x3f5c179b
#4
0x0f6795d9
· blocks 1
#6
0x39435dac
#7
updateDataFeedsValuesPartial
#8
0x39435dac
#9
setData
#10
0x59558d29
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88e771e8…7d4a
0x34b655…2a6f
4 touches
1 conflict
0x898d9b8a…d1ef
0x34b655…2a6f
4 touches
1 conflict
0xa0d3a786…91d9
0x34b655…2a6f
4 touches
1 conflict
0x5b17482f…0dc4
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x007b42ba…13dc
0x34b655…2a6f
2 touches
0 conflicts
0x00a010e9…025e
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…0004
0x546d22…8146
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
0x88e771e8ba…5c7d4a
Audit this contract →
← previous block
·
next block →
recent activity