pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,794,175
← previous block
next block →
recent activity
Analyzing
Block #82,794,175
10 transactions · 6 stateful · 2026-06-21 18:41:34 UTC
Parallelism
70
/100
Blocked
33
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,794,175
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0f6795d9
· blocks 2
#3
0x0f6795d9
#4
0x0f6795d9
#5
receiveMessage
#7
0x0f6795d9
#8
updateDataFeedsValuesPartial
#9
setData
#2
0x0f6795d9
· blocks 1
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b305a3b…1c35
0x34b655…2a6f
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09f51362…ebb2
0x34b655…2a6f
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x18dc3f96…0d05
0x34b655…2a6f
2 touches
0 conflicts
0x1fac1198…caf1
0x34b655…2a6f
2 touches
0 conflicts
0x30c5329c…711c
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
3 conflicts on slot
0x8b305a3b6b…0c1c35
Audit this contract →
← previous block
·
next block →
recent activity