pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,978,248
← previous block
next block →
recent activity
Analyzing
Block #90,978,248
11 transactions · 10 stateful · 2026-07-28 05:47:35 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,978,248
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x0c7abd22
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
· blocks 1
#7
0x3f5c179b
#8
0xed82b078
#9
setData
#10
0x39435dac
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42d5e8f3…5930
0x34b655…2a6f
4 touches
1 conflict
0x818e1296…f4d7
0x34b655…2a6f
4 touches
1 conflict
0x8b7fbe3c…2926
0x34b655…2a6f
3 touches
1 conflict
0x8f478f26…9d56
0x000000…012a
2 touches
0 conflicts
0x984bf48e…65c7
0x000000…012a
2 touches
0 conflicts
0x00000000…0004
0x06d045…f107
2 touches
0 conflicts
0x00000000…0007
0x06d045…f107
2 touches
0 conflicts
0x00000000…000d
0x06d045…f107
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
0x42d5e8f3e6…905930
Audit this contract →
← previous block
·
next block →
recent activity