pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#89,404,475
← previous block
next block →
recent activity
Analyzing
Block #89,404,475
9 transactions · 9 stateful · 2026-07-22 10:29:57 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,404,475
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x0f6795d9
· blocks 1
#3
0x0f6795d9
#4
0xc925b3a5
#6
0x5339c59f
#7
0x6a609c1c
#8
setData
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4fc141d9…bb36
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721c
0x34b655…2a6f
4 touches
1 conflict
0xd3980454…6341
0x34b655…2a6f
4 touches
1 conflict
0xe5f91a11…dba7
0x34b655…2a6f
4 touches
1 conflict
0x4fc141d9…bb37
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x578347c5…cb6e
0x34b655…2a6f
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
0x4fc141d9d5…c7bb36
Audit this contract →
← previous block
·
next block →
recent activity