pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,159,514
← previous block
next block →
recent activity
Analyzing
Block #92,159,514
10 transactions · 8 stateful · 2026-08-01 08:53:12 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,159,514
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0x0f6795d9
· blocks 1
#3
0x0f6795d9
#5
approve
#6
0x0f6795d9
#7
updateDataFeedsValuesPartial
#8
0x8b80a919
#9
setData
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0xb4317885…7775
0x34b655…2a6f
4 touches
1 conflict
0x068934bf…4f42
0x34b655…2a6f
3 touches
1 conflict
0x2a949bb2…8769
0x34b655…2a6f
2 touches
0 conflicts
0x4755fafb…859b
0x34b655…2a6f
2 touches
0 conflicts
0x4dda03d2…fe0d
0x34b655…2a6f
2 touches
0 conflicts
0x57330c5d…9973
0x34b655…2a6f
2 touches
0 conflicts
0x636d143c…2ccb
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
0x31b3992285…921e66
Audit this contract →
← previous block
·
next block →
recent activity