pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,958,642
← previous block
next block →
recent activity
Analyzing
Block #91,958,642
18 transactions · 17 stateful · 2026-07-31 16:02:55 UTC
Parallelism
89
/100
Blocked
6
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,958,642
· 18 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0xab083028
#3
multicall
#4
transfer
#5
transfer
· blocks 1
#7
0x0f6795d9
#8
0x3f5c179b
#9
0x3f5c179b
#10
0x0f6795d9
#11
0x39435dac
#12
0x39435dac
#13
0x6a6cc7a7
#14
transfer
#15
setData
#16
0x39435dac
#17
0x59558d29
#6
transfer
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
0xeaced15b…2221
0x754704…b603
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…000a
0x1b5fbe…500f
2 touches
0 conflicts
0x00000000…000b
0x1b5fbe…500f
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x1d10e771…bb26
0x3bd359…433a
2 touches
0 conflicts
0x49b12261…ad19
0x3bd359…433a
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:
USDC (USDC)
1 conflict on slot
0xeaced15b26…bf2221
Audit this contract →
← previous block
·
next block →
recent activity