pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,339,854
← previous block
next block →
recent activity
Analyzing
Block #76,339,854
7 transactions · 6 stateful · 2026-05-22 21:13:25 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,339,854
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xaf47a8bb
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
#5
0x0f6795d9
#6
setData
#2
0xaf47a8bb
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67d846dd…358c
0xe4c0aa…7777
4 touches
1 conflict
0x12a9b76e…cb76
0x3bd359…433a
4 touches
1 conflict
0x44ed742f…63f5
0x3bd359…433a
4 touches
1 conflict
0x4eb758b8…b13b
0x3bd359…433a
4 touches
1 conflict
0x7cf5136f…ba69
0x9f3832…4ae4
4 touches
1 conflict
0xb904490e…46c4
0x9f3832…4ae4
4 touches
1 conflict
0xd9cae1f5…327a
0x9f3832…4ae4
4 touches
1 conflict
0xd9cae1f5…327b
0x9f3832…4ae4
4 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:
0xe4c0aa41…217777
1 conflict on slot
0x67d846dda0…aa358c
Audit this contract →
← previous block
·
next block →
recent activity