pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,482,912
← previous block
next block →
recent activity
Analyzing
Block #74,482,912
8 transactions · 6 stateful · 2026-05-14 06:30:29 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,482,912
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x3fb17519
#3
0x98717539
· blocks 1
#4
updateDataFeedsValuesPartial
#5
setData
#6
0xd6ad8b…0e3e
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x742436a7…c4d4
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x482682a4…67d9
0x065c9d…c394
2 touches
0 conflicts
0x949162f7…8b95
0x065c9d…c394
2 touches
0 conflicts
0xb0bee6d1…b099
0x065c9d…c394
2 touches
0 conflicts
0xbe6f9b37…b37d
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:
0x34b6552d…112a6f
1 conflict on slot
0x742436a7e5…69c4d4
Audit this contract →
← previous block
·
next block →
recent activity