pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,769,978
← previous block
next block →
recent activity
Analyzing
Block #91,769,978
11 transactions · 11 stateful · 2026-07-31 00:13:44 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,769,978
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
reallocate
#2
updatePrices
#3
0x0c7abd22
· blocks 1
#4
0x7c51d6cf
#5
0x3f5c179b
#6
0x3f5c179b
#7
0x0f6795d9
#8
setData
#10
0x59558d29
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36a76bd2…1fb0
0x34b655…2a6f
4 touches
1 conflict
0x5fe7e126…6dd2
0x34b655…2a6f
4 touches
1 conflict
0xab92d92c…c8bf
0x34b655…2a6f
4 touches
1 conflict
0xed59b1cd…8509
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001e
0x1b6862…e19c
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
0x36a76bd264…b01fb0
Audit this contract →
← previous block
·
next block →
recent activity