pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#89,693,884
← previous block
next block →
recent activity
Analyzing
Block #89,693,884
9 transactions · 8 stateful · 2026-07-23 17:43:27 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,693,884
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
0x3f5c179b
#3
0x3f5c179b
#4
0x0f6795d9
· blocks 1
#6
setData
#7
0xce5772…e321
#5
0x0f6795d9
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30e3f228…0d43
0x34b655…2a6f
4 touches
1 conflict
0x91f687f3…aca8
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0291b96b…587b
0x34b655…2a6f
2 touches
0 conflicts
0x16b2c220…a431
0x34b655…2a6f
2 touches
0 conflicts
0x316fa031…d758
0x34b655…2a6f
2 touches
0 conflicts
0x37ee41fb…4651
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
0x30e3f2288d…4d0d43
Audit this contract →
← previous block
·
next block →
recent activity