pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,701,594
← previous block
next block →
recent activity
Analyzing
Block #82,701,594
10 transactions · 8 stateful · 2026-06-21 08:23:40 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,701,594
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x5ddf3a9c
#3
setData
#4
0x39435dac
· blocks 1
#6
0x39435dac
#7
0x39435dac
#8
0x39435dac
#9
0xc7e3ec2c
#5
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x97a0cd85…cfca
0x080ec9…fe74
2 touches
0 conflicts
0xa0bab64e…b8c0
0x080ec9…fe74
2 touches
0 conflicts
0x00000000…0008
0x14c8e4…fdcb
2 touches
0 conflicts
0x00000000…0009
0x14c8e4…fdcb
2 touches
0 conflicts
0x00000000…000a
0x14c8e4…fdcb
2 touches
0 conflicts
0x089b1065…19b9
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
1 conflict on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity