pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,685,443
← previous block
next block →
recent activity
Analyzing
Block #94,685,443
10 transactions · 10 stateful · 2026-08-10 04:55:19 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,685,443
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
0x5acec890
#3
0x0f6795d9
· blocks 2
#6
metacall
#7
0x3f5c179b
#8
0x6a795a2e
#9
setData
#4
0x0f6795d9
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2e52e46…0894
0x34b655…2a6f
4 touches
1 conflict
0x2c539d94…b63a
0x34b655…2a6f
4 touches
1 conflict
0x4abaedb1…65b9
0x34b655…2a6f
4 touches
1 conflict
0x8d175439…fb79
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2db
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2dc
0x34b655…2a6f
4 touches
1 conflict
0xb0608dfe…083d
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
0xe2e52e4663…6f0894
Audit this contract →
← previous block
·
next block →
recent activity