pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,445,953
← previous block
next block →
recent activity
Analyzing
Block #76,445,953
9 transactions · 6 stateful · 2026-05-23 09:00:03 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,445,953
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0f6795d9
#2
0x0f6795d9
#3
updateDataFeedsValuesPartial
#4
executeBatch
· blocks 2
#7
0x0f6795d9
#8
setData
#5
executeBatch
· blocks 1
#6
executeBatch
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
0xf79df061…e005
0xe52b14…7230
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x48e4e1cf…f91b
0x34b655…2a6f
2 touches
0 conflicts
0x4d8676eb…e320
0x34b655…2a6f
2 touches
0 conflicts
0x53d1f845…4e58
0x34b655…2a6f
2 touches
0 conflicts
0x56b64ca6…0f43
0x34b655…2a6f
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:
0xe52b1424…bb7230
3 conflicts on slot
0xf79df061c7…91e005
Audit this contract →
← previous block
·
next block →
recent activity