pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,985,054
← previous block
next block →
recent activity
Analyzing
Block #75,985,054
9 transactions · 7 stateful · 2026-05-21 05:50:25 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,985,054
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
setData
#3
0x39abec6b
#4
0xed82b078
#5
0x54147c…c1d1
#6
0xb38d80…b935
#7
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d0e98f3…7ba0
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x676f9f01…a8ac
0x34b655…2a6f
4 touches
1 conflict
0x0134444b…cd57
0x2ab50b…5c41
2 touches
0 conflicts
0x0230870e…327e
0x2ab50b…5c41
2 touches
0 conflicts
0x047d8971…c728
0x2ab50b…5c41
2 touches
0 conflicts
0x06ebedbb…7da4
0x2ab50b…5c41
2 touches
0 conflicts
0x07d64d54…6bfc
0x2ab50b…5c41
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
0x8d0e98f3a2…177ba0
Audit this contract →
← previous block
·
next block →
recent activity