pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,573,109
← previous block
next block →
recent activity
Analyzing
Block #90,573,109
11 transactions · 11 stateful · 2026-07-26 19:49:20 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,573,109
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39ecce49
· blocks 1
#2
0xab083028
#3
postPriceList
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
· blocks 1
#8
0x6a666537
#9
setData
#10
0x39435dac
#6
0x0f6795d9
#7
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0x510e44…2cd9
4 touches
1 conflict
0x44ed742f…63f5
0x3bd359…433a
4 touches
1 conflict
0x4eb758b8…b13b
0x3bd359…433a
4 touches
1 conflict
0xc9d85869…8531
0x3bd359…433a
4 touches
1 conflict
0x3940d757…7df8
0xe1c8b7…3022
4 touches
1 conflict
0xa164d951…1534
0xe1c8b7…3022
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf45a6126…89bf
0x436662…7777
4 touches
1 conflict
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:
0x510e448c…882cd9
1 conflict on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity