pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,985,925
← previous block
next block →
recent activity
Analyzing
Block #73,985,925
11 transactions · 6 stateful · 2026-05-11 23:22:36 UTC
Parallelism
82
/100
Blocked
17
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,985,925
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0x5bf9264c
#3
0x5bf9264c
#4
0x6a026534
#5
0xe8c9df…642e
#6
0x52920a…27a5
#7
setData
#8
0x32366535
#9
0x39435dac
· blocks 1
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37d49489…9309
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0x64461c10…e86d
0x34b655…2a6f
2 touches
0 conflicts
0x7170c140…36bc
0x34b655…2a6f
2 touches
0 conflicts
0x85a88798…f85e
0x34b655…2a6f
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
0x37d494895c…549309
Audit this contract →
← previous block
·
next block →
recent activity