pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#90,043,175
← previous block
next block →
recent activity
Analyzing
Block #90,043,175
11 transactions · 11 stateful · 2026-07-24 23:03:47 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,043,175
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xd60faa87
#2
0xab083028
#3
0x0f6795d9
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x0f6795d9
#7
0x1fe271b4
#9
0x6a63efca
#10
setData
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89935301…af69
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…0001
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…0003
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…000a
0x04ddf6…7f33
2 touches
0 conflicts
0x446f2734…8b54
0x0a3323…0a3c
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
0x8993530124…aaaf69
Audit this contract →
← previous block
·
next block →
recent activity