pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#83,658,847
← previous block
next block →
recent activity
Analyzing
Block #83,658,847
11 transactions · 10 stateful · 2026-06-25 18:58:54 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,658,847
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
0xab083028
#3
0xab083028
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
0x0f6795d9
· blocks 1
#7
executeBatch
#8
0x0c7abd22
#10
setData
#9
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb99958f6…ccf1
0x34b655…2a6f
4 touches
1 conflict
0xc8fec9ca…2d60
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xb99958f6…ccf0
0x34b655…2a6f
4 touches
1 conflict
0xb15019ef…95ed
0x34b655…2a6f
3 touches
1 conflict
0xe1137dcf…ccb2
0x34b655…2a6f
3 touches
1 conflict
0xb7fefa89…54dc
0x754704…b603
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
0xb99958f6c8…c6ccf1
Audit this contract →
← previous block
·
next block →
recent activity