pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,855,291
← previous block
next block →
recent activity
Analyzing
Block #93,855,291
13 transactions · 12 stateful · 2026-08-07 07:03:42 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,855,291
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
#2
permit2TransferAndMulticall
#3
0x5acec890
#4
0x0f6795d9
#5
0x3f5c179b
#6
0x3f5c179b
· blocks 1
#8
updateDataFeedsValuesPartial
#9
0x6a7583c6
#10
transfer
#11
setData
#12
0x39435dac
#7
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x15073066…40a5
0x34b655…2a6f
2 touches
0 conflicts
0x15489204…b558
0x34b655…2a6f
2 touches
0 conflicts
0x25d292ed…5531
0x34b655…2a6f
2 touches
0 conflicts
0x3661f59a…874a
0x34b655…2a6f
2 touches
0 conflicts
0x42381268…420e
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:
0x40c49f17…d22af0
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity