pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,640,983
← previous block
next block →
recent activity
Analyzing
Block #82,640,983
11 transactions · 9 stateful · 2026-06-21 01:38:04 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
#82,640,983
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x9e76c652
#4
setData
#5
withdraw
#6
0x39435dac
· blocks 1
#7
0x39435dac
#8
0x39435dac
#9
0x39435dac
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x286711a5…b3bf
0x34b655…2a6f
4 touches
1 conflict
0x443f058a…ec43
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfab1627b…b819
0x34b655…2a6f
4 touches
1 conflict
0x1cefae97…7f45
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x0eff4754…f974
0x2ab50b…5c41
2 touches
0 conflicts
0x152ec6b7…3de3
0x2ab50b…5c41
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
0x286711a50a…edb3bf
Audit this contract →
← previous block
·
next block →
recent activity