pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,386,039
17 transactions · 13 stateful · 2026-05-13 19:45:41 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,386,039 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w011w112w013w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x08de772c…8e84
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x6c776dd9…c231
0x40c49f…2af0
3 touches
1 conflict
0x836874a1…b67f
0x19f079…1d56
2 touches
0 conflicts
0x51ca3051…0972
0x3bd359…433a
2 touches
0 conflicts
0x76f2524a…306c
0x3bd359…433a
2 touches
0 conflicts
0x99f666e3…b2a2
0x3bd359…433a
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: 0x065c9d28…a9c394
1 conflict on slot 0x47b807a243…c53307
Audit this contract →
← previous block·next block →recent activity