pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#89,750,335
← previous block
next block →
recent activity
Analyzing
Block #89,750,335
8 transactions · 8 stateful · 2026-07-23 22:28:24 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,750,335
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x5a5d9a99
#3
0x0f6795d9
#4
0x0f6795d9
· blocks 1
#6
setData
#7
0x6a629600
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94a77fc9…7577
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x2f0fe1df…da8a
0x34b655…2a6f
4 touches
1 conflict
0x2f0fe1df…da89
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xf7a76f16…a4ab
0x34b655…2a6f
3 touches
1 conflict
0xe679c9ea…e3a2
0x34b655…2a6f
3 touches
1 conflict
0xb6fcbbb7…2b31
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
0x94a77fc9e5…6c7577
Audit this contract →
← previous block
·
next block →
recent activity