pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,303,558
← previous block
next block →
recent activity
Analyzing
Block #74,303,558
8 transactions · 6 stateful · 2026-05-13 10:37:06 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,303,558
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
0x6a0454c9
#4
setData
#5
0xa7529e…2e1e
#6
0x39435dac
· blocks 1
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb1747e2…f78b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x000761bd…734d
0x065c9d…c394
2 touches
0 conflicts
0x24968e6d…0132
0x065c9d…c394
2 touches
0 conflicts
0x3a5f8ae1…7f91
0x065c9d…c394
2 touches
0 conflicts
0x48a085c4…f848
0x065c9d…c394
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
0xbb1747e217…82f78b
Audit this contract →
← previous block
·
next block →
recent activity