pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,240,822
← previous block
next block →
recent activity
Analyzing
Block #76,240,822
9 transactions · 6 stateful · 2026-05-22 10:14:24 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,240,822
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39ecce49
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x5bf9264c
#4
0x5bf9264c
#5
setData
#7
0xed82b078
#8
0x34653439
#6
0xaf47a8bb
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa164d951…1534
0xe1c8b7…3022
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
0x67d846dd…358c
0x3ecdfa…7777
4 touches
1 conflict
0x7cf5136f…ba69
0x9f3832…4ae4
4 touches
1 conflict
0xcb25539d…835c
0x9f3832…4ae4
4 touches
1 conflict
0xcb25539d…835d
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:
0xe1c8b733…e33022
1 conflict on slot
0xa164d95170…fa1534
Audit this contract →
← previous block
·
next block →
recent activity