pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,396,938
← previous block
next block →
recent activity
Analyzing
Block #76,396,938
8 transactions · 6 stateful · 2026-05-23 03:34:05 UTC
Parallelism
63
/100
Blocked
33
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,396,938
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
setData
#4
0x45761772
· blocks 2
#7
0x9b5c6d…2a70
#5
0x45761772
· blocks 1
#6
0x45761772
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x405787fa…eef1
0x46a15b…4364
6 touches
3 conflicts
0x00000000…000d
0x46a15b…4364
6 touches
3 conflicts
0x405787fa…eef0
0x46a15b…4364
6 touches
3 conflicts
0x405787fa…eee0
0x46a15b…4364
4 touches
1 conflict
0x405787fa…eee1
0x46a15b…4364
4 touches
1 conflict
0x8b5736b5…a74b
0x46a15b…4364
3 touches
1 conflict
0x79fe8870…1f37
0x46a15b…4364
3 touches
1 conflict
0xef1a64be…9a4b
0x46a15b…4364
3 touches
1 conflict
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:
0x46a15b0b…7f4364
3 conflicts on slot
0x405787fa12…bbeef1
Audit this contract →
← previous block
·
next block →
recent activity