pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,963,233
← previous block
next block →
recent activity
Analyzing
Block #94,963,233
12 transactions · 11 stateful · 2026-08-11 04:14:03 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,963,233
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
· blocks 1
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
allocate
#6
0x0f6795d9
#7
0x0f6795d9
#8
0xed82b078
#9
0x6a7aa203
#10
transfer
#11
setData
#2
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd4bcf904…38ea
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x4bc1abab…5874
0x34b655…2a6f
3 touches
1 conflict
0xd2c28f18…87b9
0x34b655…2a6f
3 touches
1 conflict
0xe74d8286…be05
0x2b5cd4…1a0a
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
0xd4bcf90418…ff38ea
Audit this contract →
← previous block
·
next block →
recent activity