pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,836,493
← previous block
next block →
recent activity
Analyzing
Block #89,836,493
12 transactions · 11 stateful · 2026-07-24 05:43:15 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,836,493
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x8263f5d9
#3
0x5a5d9a99
#4
execFwdPositionOps
· blocks 1
#6
0x3f5c179b
#7
execFwdPositionOps
#8
0xce1e7030
· blocks 1
#10
0x6a62fbeb
#11
setData
#5
execFwdPositionOps
#9
0xce1e7030
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x392a02b5…0019
0x81a224…7777
4 touches
1 conflict
0x00000000…0003
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0000
0x714a26…182d
4 touches
1 conflict
0x00000000…0001
0x714a26…182d
4 touches
1 conflict
0x00000000…0003
0x714a26…182d
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0xddc22bc2…7f7a
0x754704…b603
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:
0x81a224f8…0b7777
1 conflict on slot
0x392a02b5dd…cf0019
Audit this contract →
← previous block
·
next block →
recent activity