pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,527,057
← previous block
next block →
recent activity
Analyzing
Block #76,527,057
9 transactions · 8 stateful · 2026-05-23 18:00:03 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,527,057
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
#2
updateDataFeedsValuesPartial
#3
0x98717539
#4
executeBatch
· blocks 1
#6
0x8263f5d9
#7
setData
#8
delegate
#5
executeBatch
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x3f68ccb5…e301
0xe52b14…7230
4 touches
1 conflict
0x58733c38…f2cd
0xe52b14…7230
4 touches
1 conflict
0x693b762e…1fcd
0xe52b14…7230
4 touches
1 conflict
0x6a3749da…c493
0xe52b14…7230
4 touches
1 conflict
0x6ad5feb6…5606
0xe52b14…7230
4 touches
1 conflict
0xa01610d9…2ed3
0xe52b14…7230
4 touches
1 conflict
0xc4a2f619…eb38
0xe52b14…7230
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:
0xe52b1424…bb7230
1 conflict on slot
0xf79df061c7…91e005
Audit this contract →
← previous block
·
next block →
recent activity