pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,848,300
← previous block
next block →
recent activity
Analyzing
Block #93,848,300
9 transactions · 7 stateful · 2026-08-07 06:28:33 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,848,300
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
handleOps
#3
executeBatch
#4
0x0f6795d9
#5
0x0f6795d9
#6
setData
#7
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fab7fbe…1ce5
0x34b655…2a6f
4 touches
1 conflict
0xc751242c…efac
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x06b47f1c…6177
0x000000…a032
2 touches
0 conflicts
0x0f2dbfa6…8699
0x000000…a032
2 touches
0 conflicts
0x21a5ce88…38fc
0x000000…a032
2 touches
0 conflicts
0x250db8bc…c98d
0x000000…a032
2 touches
0 conflicts
0x36eaf5cb…7654
0x000000…a032
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
0x5fab7fbe22…391ce5
Audit this contract →
← previous block
·
next block →
recent activity