pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#90,458,979
← previous block
next block →
recent activity
Analyzing
Block #90,458,979
9 transactions · 8 stateful · 2026-07-26 10:15:12 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
#90,458,979
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x5a5d9a99
· blocks 1
#4
0x5a5d9a99
#5
0x3f5c179b
#6
0x4d8dc985
#7
0x0f6795d9
#8
setData
#3
0x5a5d9a99
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
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1f40ac22…24cb
0x34b655…2a6f
2 touches
0 conflicts
0x33fa9eab…4b3d
0x34b655…2a6f
2 touches
0 conflicts
0x3ca9a061…1f41
0x34b655…2a6f
2 touches
0 conflicts
0x3cb8c8c3…22f4
0x34b655…2a6f
2 touches
0 conflicts
0x3d4c0233…20a5
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
1 conflict on slot
0x6fe7d366be…a578ff
Audit this contract →
← previous block
·
next block →
recent activity