pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,179,984
← previous block
next block →
recent activity
Analyzing
Block #82,179,984
8 transactions · 7 stateful · 2026-06-18 22:20:25 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,179,984
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
setData
#3
0x3f5c179b
#4
0x6a346fa1
#5
0x39435dac
· blocks 1
#7
0xc7e3ec2c
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xada5ad75…1d24
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x01b6579d…7ed7
0x34b655…2a6f
2 touches
0 conflicts
0x17479931…e196
0x34b655…2a6f
2 touches
0 conflicts
0x55c1a07a…51ea
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
0xada5ad75a3…de1d24
Audit this contract →
← previous block
·
next block →
recent activity