pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,537,487
← previous block
next block →
recent activity
Analyzing
Block #106,537,487
7 transactions · 6 stateful · 2026-09-20 18:42:11 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,537,487
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b93d8…5225
#2
setData
#3
execFwdPositionOpsV2
#4
0x6ab02906
#5
0x61d59c2d
· blocks 1
#6
0x61d59c2d
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3abe489…ebf2
0x4de0d8…bfc3
4 touches
1 conflict
0xe3abe489…ebf3
0x4de0d8…bfc3
4 touches
1 conflict
0xe3abe489…ebf5
0x4de0d8…bfc3
4 touches
1 conflict
0xe3abe489…ebf6
0x4de0d8…bfc3
4 touches
1 conflict
0xe3abe489…ebf8
0x4de0d8…bfc3
4 touches
1 conflict
0xe3abe489…ebf9
0x4de0d8…bfc3
4 touches
1 conflict
0x4073f47e…39e5
0x34b655…2a6f
2 touches
0 conflicts
0x4073f47e…39e6
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:
0x4de0d89d…36bfc3
1 conflict on slot
0xe3abe4895e…e5ebf2
Audit this contract →
← previous block
·
next block →
recent activity