pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,874,895
← previous block
next block →
recent activity
Analyzing
Block #100,874,895
6 transactions · 6 stateful · 2026-08-31 22:26:55 UTC
Parallelism
67
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,874,895
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x59558d29
#3
execFwdPositionOpsV2
· blocks 1
#5
0x6a960026
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38befc08…20c8
0x34b655…2a6f
4 touches
1 conflict
0x98862f54…62ca
0x34b655…2a6f
4 touches
1 conflict
0xa020506f…7c60
0x34b655…2a6f
4 touches
1 conflict
0xde54926c…1c87
0x34b655…2a6f
4 touches
1 conflict
0x03513f1e…a4f9
0x34b655…2a6f
2 touches
0 conflicts
0x29261c42…c87a
0x34b655…2a6f
2 touches
0 conflicts
0x33b5035a…d1c6
0x34b655…2a6f
2 touches
0 conflicts
0x3e4b4b6b…433e
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
0x38befc0864…cc20c8
Audit this contract →
← previous block
·
next block →
recent activity