pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,330,128
← previous block
next block →
recent activity
Analyzing
Block #99,330,128
24 transactions · 16 stateful · 2026-08-26 12:34:17 UTC
Parallelism
83
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,330,128
· 24 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
#2
0x0c7abd22
#3
0x0c7abd22
#4
0xab083028
· blocks 1
#6
0x8263f5d9
#7
execOrders
#8
execOrders
#9
0x5acec890
#10
execPerpOps
#11
execPerpOps
#12
0x0c7abd22
#13
execFwdPositionOpsV2
#14
0x3f5c179b
#15
0x3f5c179b
#16
0x3f5c179b
· blocks 2
#17
0xaf47a8bb
#21
commit
#22
setData
#23
execOrders
#5
0xab083028
· blocks 1
#18
0xed82b078
· blocks 1
#19
0xed82b078
· blocks 1
#20
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
16
w0
18
w1
19
w2
20
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x065ff70b…356d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x10b1199e…343b
0x40c49f…2af0
3 touches
1 conflict
0xa987699f…eabe
0x2b46c0…1669
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:
0x40c49f17…d22af0
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity