pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,676,018
← previous block
next block →
recent activity
Analyzing
Block #89,676,018
9 transactions · 8 stateful · 2026-07-23 16:13:13 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,676,018
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x0f6795d9
· blocks 1
#3
0x3f5c179b
#4
0xce1e7030
· blocks 1
#6
forward
#7
updateDataFeedsValuesPartial
#5
0xce1e7030
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w0
5
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e4db5a4…82dc
0x2a68ba…90c5
4 touches
1 conflict
0x94ba9c4a…41d8
0x34b655…2a6f
4 touches
1 conflict
0xddc22bc2…7f7a
0x754704…b603
4 touches
1 conflict
0x6882c020…1910
0x81a224…7777
4 touches
1 conflict
0xa23f71b6…61df
0xe7a4f9…4b2d
4 touches
1 conflict
0xd2c68ceb…09c4
0xe7a4f9…4b2d
4 touches
1 conflict
0x213ee207…a151
0x2b46c0…1669
2 touches
0 conflicts
0x46279ae7…20dd
0x2b46c0…1669
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x2e4db5a4ed…8f82dc
Audit this contract →
← previous block
·
next block →
recent activity