pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#90,044,164
← previous block
next block →
recent activity
Analyzing
Block #90,044,164
7 transactions · 6 stateful · 2026-07-24 23:08:46 UTC
Parallelism
57
/100
Blocked
33
%
Avg conflicts / tx
0.43
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,044,164
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 2
#3
0x0f6795d9
#6
setData
#4
0x0f6795d9
· blocks 1
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf8a748aa…446a
0x34b655…2a6f
4 touches
1 conflict
0xfb4f6c11…7103
0x34b655…2a6f
4 touches
1 conflict
0x01078ee0…48e1
0x34b655…2a6f
2 touches
0 conflicts
0x20ead41b…0c34
0x34b655…2a6f
2 touches
0 conflicts
0x21f1c80a…7650
0x34b655…2a6f
2 touches
0 conflicts
0x277c71c7…8cc7
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:
Perpl
3 conflicts on slot
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity