pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,186,936
← previous block
next block →
recent activity
Analyzing
Block #92,186,936
10 transactions · 10 stateful · 2026-08-01 11:11:06 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,186,936
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x5acec890
#3
0x0f6795d9
#4
0x0f6795d9
#5
0x0f6795d9
#6
harvest
#7
setData
#8
0x59558d29
· blocks 1
#9
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0x44b80fe8…bfa7
0x34b655…2a6f
2 touches
0 conflicts
0x5b450c7f…95ee
0x34b655…2a6f
2 touches
0 conflicts
0x666f54f8…873c
0x34b655…2a6f
2 touches
0 conflicts
0x83158702…eb58
0x34b655…2a6f
2 touches
0 conflicts
0x9cd33a29…fef8
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:
0x80c74517…647210
1 conflict on slot
0x0000000000…00004b
Audit this contract →
← previous block
·
next block →
recent activity