pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,552,580
← previous block
next block →
recent activity
Analyzing
Block #102,552,580
6 transactions · 6 stateful · 2026-09-06 19:32:27 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.33
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,552,580
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
0x0c7abd22
· blocks 2
#5
execFwdPositionOpsV2
#3
0x4cb2db39
#4
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004f
0x80c745…7210
4 touches
1 conflict
0x00000000…0050
0x80c745…7210
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
2 touches
0 conflicts
0x2825c4f2…f77f
0x01bff4…1071
2 touches
0 conflicts
0x7ab0b5f5…39e2
0x01bff4…1071
2 touches
0 conflicts
0x09beabbc…065c
0x188d58…ea8e
2 touches
0 conflicts
0x09beabbc…065e
0x188d58…ea8e
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:
0x80c74517…647210
1 conflict on slot
0x0000000000…00004f
Audit this contract →
← previous block
·
next block →
recent activity