pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,846,201
← previous block
next block →
recent activity
Analyzing
Block #89,846,201
11 transactions · 11 stateful · 2026-07-24 06:32:15 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
#89,846,201
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x50a0b275
· blocks 1
#2
updateDataFeedsValuesPartial
#4
0x0f6795d9
#5
0x0f6795d9
#6
0x0f6795d9
#7
0x39435dac
#8
0x6a630767
#9
setData
#10
0x39435dac
#3
0x62be7533
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd43be87…f667
0xe1c8b7…3022
4 touches
1 conflict
0x44ed742f…63f5
0x3bd359…433a
4 touches
1 conflict
0x4eb758b8…b13b
0x3bd359…433a
4 touches
1 conflict
0xc6101b5d…4361
0x3bd359…433a
4 touches
1 conflict
0x5504f74a…6874
0x43cf54…7777
4 touches
1 conflict
0x00000000…0004
0x48c3bb…b17b
4 touches
1 conflict
0xa164d951…1534
0xe1c8b7…3022
4 touches
1 conflict
0x68faa0b9…14af
0x368ee5…7ca4
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:
0xe1c8b733…e33022
1 conflict on slot
0xdd43be87b3…92f667
Audit this contract →
← previous block
·
next block →
recent activity