pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#91,025,219
← previous block
next block →
recent activity
Analyzing
Block #91,025,219
9 transactions · 8 stateful · 2026-07-28 09:44:44 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
#91,025,219
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 2
#7
setData
#8
0xc7e3ec2c
#5
0x0f6795d9
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4041c86…a637
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…642d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xc4c059d8…185d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x12e5ded5…a9d1
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0xa4041c86dd…3ca637
Audit this contract →
← previous block
·
next block →
recent activity