pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,372,931
← previous block
next block →
recent activity
Analyzing
Block #94,372,931
9 transactions · 8 stateful · 2026-08-09 02:38:39 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,372,931
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0x0f6795d9
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#7
batchUpdate
#8
setData
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x2bea6eae…9f7b
0x34b655…2a6f
4 touches
1 conflict
0x0661e5b9…8a09
0x34b655…2a6f
2 touches
0 conflicts
0x1e737223…2278
0x34b655…2a6f
2 touches
0 conflicts
0x206f4379…e08a
0x34b655…2a6f
2 touches
0 conflicts
0x282f129e…8f33
0x34b655…2a6f
2 touches
0 conflicts
0x4633fac1…c113
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity