pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,137,556
← previous block
next block →
recent activity
Analyzing
Block #100,137,556
45 transactions · 43 stateful · 2026-08-29 08:33:02 UTC
Parallelism
96
/100
Blocked
2
%
Avg conflicts / tx
0.02
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,137,556
· 45 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x5acec890
#4
0x4be850b3
#5
0x59558d29
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
setData
#9
0x3f5c179b
#10
CreateUser
#11
CreateMemory
#12
CreateUser
#13
CreateMemory
#14
CreateUser
#15
CreateMemory
#16
CreateMemory
#17
CreateMemory
#18
CreateMemory
#19
CreateMemory
#20
CreateMemory
#21
CreateMemory
#22
CreateMemory
#23
CreateMemory
#24
CreateMemory
#25
CreateMemory
#26
CreateMemory
#27
CreateMemory
#28
CreateMemory
#29
CreateMemory
#30
CreateMemory
#31
CreateMemory
#32
CreateMemory
#33
CreateMemory
#34
CreateMemory
#35
CreateMemory
#36
CreateMemory
#37
CreateMemory
#38
CreateMemory
#39
CreateMemory
#40
CreateMemory
#41
CreateMemory
#42
CreateMemory
#43
0xed82b078
#44
execFwdPositionOpsV2
#2
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x2bbc0cfb…c2c0
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
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:
ShMonad (shMON)
1 conflict on slot
0x0000000000…000013
Audit this contract →
← previous block
·
next block →
recent activity