pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,957,335
← previous block
next block →
recent activity
Analyzing
Block #91,957,335
11 transactions · 11 stateful · 2026-07-31 15:56:21 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,957,335
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
withdraw
#2
0x5a5d9a99
· blocks 1
#3
0x0f6795d9
· blocks 1
#4
0x3f5c179b
#6
0x57368ddf
#7
updateDataFeedsValuesPartial
#8
setData
#10
0x59558d29
#5
0x0f6795d9
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
5
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x565875e6…e2a1
0x34b655…2a6f
4 touches
1 conflict
0xb514ce62…3397
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca608d0c…f23b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0005
0x7821ba…01d0
2 touches
0 conflicts
0x00000000…0008
0x7821ba…01d0
2 touches
0 conflicts
0x00000000…000b
0x7821ba…01d0
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
0x565875e62c…7fe2a1
Audit this contract →
← previous block
·
next block →
recent activity