pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,241,619
← previous block
next block →
recent activity
Analyzing
Block #74,241,619
10 transactions · 6 stateful · 2026-05-13 03:45:06 UTC
Parallelism
80
/100
Blocked
33
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,241,619
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
setData
#2
updateDataFeedsValuesPartial
#3
withdraw
#4
forward
#5
0x6df9e92b
· blocks 1
#7
0x39435dac
· blocks 1
#9
jMMeC
#6
0x6df9e92b
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3ff1ab2…8ae3
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0x019883…2a9a
4 touches
1 conflict
0x00000000…0002
0x019883…2a9a
4 touches
1 conflict
0x44ad89ba…cf83
0x0cc9b2…7777
4 touches
1 conflict
0xa10c86f8…4b74
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x99a3a7c1…1e2b
0x0cc9b2…7777
4 touches
1 conflict
0xb8228d38…3953
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:
0x34b6552d…112a6f
1 conflict on slot
0xa3ff1ab2e8…2a8ae3
Audit this contract →
← previous block
·
next block →
recent activity