pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,033,031
← previous block
next block →
recent activity
Analyzing
Block #100,033,031
11 transactions · 9 stateful · 2026-08-28 23:46:39 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,033,031
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0xab083028
#3
0x6ad2e98b
#4
execOrders
#5
0x59558d29
· blocks 1
#7
repay
#8
setData
#9
execFwdPositionOpsV2
#10
0xed82b078
#6
0x59558d29
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
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x56903f42…3e48
0x000000…012a
2 touches
0 conflicts
0xd3118b0d…3ef2
0x000000…012a
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…003d
0xa6afd3…d132
2 touches
0 conflicts
0x5778d110…d2e6
0xc8689a…ee79
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…00004b
Audit this contract →
← previous block
·
next block →
recent activity