pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,552,057
← previous block
next block →
recent activity
Analyzing
Block #75,552,057
10 transactions · 9 stateful · 2026-05-19 05:43:43 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,552,057
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
execute
#3
0x6a0bf907
#4
0x98717539
· blocks 1
#6
updateDataFeedsValuesPartial
#7
setData
#9
forward
#5
0x98717539
#8
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6417de0…2191
0xc8689a…ee79
4 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x6aa624fd…a84c
0x1b6862…e19c
4 touches
1 conflict
0xb3870dbe…bef3
0x2a68ba…90c5
4 touches
1 conflict
0x313f2565…5b00
0x34b655…2a6f
4 touches
1 conflict
0x578e7f66…1b56
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:
0xc8689a47…62ee79
1 conflict on slot
0xc6417de023…802191
Audit this contract →
← previous block
·
next block →
recent activity