pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,346,527
← previous block
next block →
recent activity
Analyzing
Block #76,346,527
13 transactions · 10 stateful · 2026-05-22 21:57:50 UTC
Parallelism
77
/100
Blocked
20
%
Avg conflicts / tx
0.15
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,346,527
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
swapExactIn
#2
repay
#3
0x98717539
#4
0x0f6795d9
#5
0x0f6795d9
#6
0x0f6795d9
#7
setData
#8
0x39435dac
· blocks 1
#9
0x39435dac
#12
0x39435dac
#10
0x39435dac
· blocks 1
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
10
w1
11
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa3492db…3703
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xed18a03c…f448
0x000000…012a
2 touches
0 conflicts
0x5c87b3f0…fdbb
0x3bd359…433a
2 touches
0 conflicts
0x451f0c72…64f0
0x57ea24…2cec
2 touches
0 conflicts
0xe01fe4f0…6285
0x57ea24…2cec
2 touches
0 conflicts
0x64cdef08…6a05
0x754704…b603
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
0xaa3492db13…fc3703
Audit this contract →
← previous block
·
next block →
recent activity