pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,608,442
← previous block
next block →
recent activity
Analyzing
Block #91,608,442
11 transactions · 8 stateful · 2026-07-30 10:41:10 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,608,442
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x0f6795d9
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#5
0x94defb17
#6
0x39435dac
#7
0x39435dac
· blocks 1
#9
0x6a6b2abe
#10
setData
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x05e1eba1…6491
0x34b655…2a6f
2 touches
0 conflicts
0x068d0c9f…81f4
0x34b655…2a6f
2 touches
0 conflicts
0x075dcfb7…1c3b
0x34b655…2a6f
2 touches
0 conflicts
0x11dfcfbe…0b0f
0x34b655…2a6f
2 touches
0 conflicts
0x1b00d86a…f192
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
0xbde524f475…b143bf
Audit this contract →
← previous block
·
next block →
recent activity