pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,372,924
← previous block
next block →
recent activity
Analyzing
Block #94,372,924
11 transactions · 9 stateful · 2026-08-09 02:38:37 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,372,924
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
#2
0x5acec890
#3
0x5acec890
#4
0x5acec890
#5
exactInputSingle
#6
0x0f6795d9
· blocks 1
#8
0x6a77e8a4
#9
setData
#10
0xc7e3ec2c
#7
0x0f6795d9
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
0xeca3f7cd…57b6
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x19b340df…f4f0
0x34b655…2a6f
4 touches
1 conflict
0xeca3f7cd…57b7
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x8b2ac903…595d
0x34b655…2a6f
3 touches
1 conflict
0x275cdeb1…084f
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
0xeca3f7cd6e…1257b6
Audit this contract →
← previous block
·
next block →
recent activity