pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,719,061
← previous block
next block →
recent activity
Analyzing
Block #94,719,061
11 transactions · 10 stateful · 2026-08-10 07:44:24 UTC
Parallelism
64
/100
Blocked
30
%
Avg conflicts / tx
0.36
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,719,061
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x41a8f47c
#2
0xab083028
#3
0x5acec890
· blocks 2
#6
0x14bad976
#7
setData
#8
0x3f5c179b
#9
execFwdPositionOps
#4
0x5acec890
· blocks 1
#5
0x5acec890
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
10
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa86351b8…2c5a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xb0c603b2…e412
0x065c9d…c394
2 touches
0 conflicts
0xb33ff823…1188
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x4d1e3e31…edf8
0x3bd359…433a
2 touches
0 conflicts
0x997ccc40…4dfd
0x3bd359…433a
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
3 conflicts on slot
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity