pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,663,657
← previous block
next block →
recent activity
Analyzing
Block #93,663,657
10 transactions · 7 stateful · 2026-08-06 15:00:17 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,663,657
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
#2
0x41a8f47c
#3
updateDataFeedsValuesPartial
#4
0x222d4ad6
#5
0x0f6795d9
#6
0x0f6795d9
#7
setData
#8
0x39435dac
· blocks 1
#9
0x39435dac
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
0xe9452241…95a3
0x34b655…2a6f
4 touches
1 conflict
0x9ae859db…2d84
0x34b655…2a6f
4 touches
1 conflict
0xbd43680a…6be4
0x34b655…2a6f
4 touches
1 conflict
0x2267f8c4…a571
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x41d39318…d624
0x34b655…2a6f
2 touches
0 conflicts
0x76faab64…5da0
0x34b655…2a6f
2 touches
0 conflicts
0x97d5efed…1aa4
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
0xe945224145…7195a3
Audit this contract →
← previous block
·
next block →
recent activity