pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,159,873
← previous block
next block →
recent activity
Analyzing
Block #92,159,873
11 transactions · 11 stateful · 2026-08-01 08:55:00 UTC
Parallelism
82
/100
Blocked
27
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,159,873
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5acec890
· blocks 1
#3
executeBatch
#4
0x0f6795d9
· blocks 1
#6
setData
#7
0x6a6db4dc
#9
0x59558d29
· blocks 1
#5
0x0f6795d9
#8
0x39435dac
#10
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w0
5
w1
8
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb26ea41e…d376
0x34b655…2a6f
4 touches
1 conflict
0xd5c56995…6d21
0x34b655…2a6f
4 touches
1 conflict
0xd5c56995…6d22
0x34b655…2a6f
4 touches
1 conflict
0xefcdf197…96a2
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x3d715b82…3047
0x34b655…2a6f
4 touches
1 conflict
0x34c53903…9a57
0x34b655…2a6f
4 touches
1 conflict
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
0xb26ea41e5a…36d376
Audit this contract →
← previous block
·
next block →
recent activity