pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,438,352
← previous block
next block →
recent activity
Analyzing
Block #76,438,352
9 transactions · 7 stateful · 2026-05-23 08:09:29 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,438,352
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xeabbe9d8
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x000000b2
#4
setData
#5
0x0f6795d9
#6
0x0f6795d9
#8
0x39435dac
#7
send
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52c63247…ce02
0x0a3323…0a3c
4 touches
1 conflict
0x7ebd6e44…b6f3
0x6f4756…dd5b
4 touches
1 conflict
0x2ea01b4c…c231
0xc39161…2de7
4 touches
1 conflict
0x48e0ade2…d27a
0xc39161…2de7
4 touches
1 conflict
0xbd25225a…c493
0xc39161…2de7
4 touches
1 conflict
0xf95d4c06…c5b4
0xc39161…2de7
4 touches
1 conflict
0x00000000…0002
0x0d73bf…be07
2 touches
0 conflicts
0x00000000…0003
0x0d73bf…be07
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:
0x0a332311…6e0a3c
1 conflict on slot
0x52c63247e1…bace02
Audit this contract →
← previous block
·
next block →
recent activity