pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,984,957
← previous block
next block →
recent activity
Analyzing
Block #75,984,957
13 transactions · 9 stateful · 2026-05-21 05:49:46 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,984,957
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x98717539
· blocks 1
#4
poke
#5
poke
#6
0x0f6795d9
#7
0x0f6795d9
#8
0x366fe5db
#9
updateDataFeedsValuesPartial
#10
setData
#11
0x6e2da9…4b0f
#12
0xcc646a…d350
#3
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x1d1325…2305
2 touches
0 conflicts
0xa17ec269…7cdd
0x1d1325…2305
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:
Perpl
1 conflict on slot
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity