pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,303,229
5 transactions · 4 stateful · 2026-05-13 10:34:54 UTC
Parallelism
60/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,303,229 · 5 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x000761bd…734d
0x065c9d…c394
4 touches
1 conflict
0x0817e9b9…4490
0x065c9d…c394
3 touches
1 conflict
0xf53efa9d…588a
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x09b03240…06fb
0x065c9d…c394
2 touches
0 conflicts
0x132fbe5c…e83c
0x065c9d…c394
2 touches
0 conflicts
0x275a8b14…820a
0x065c9d…c394
2 touches
0 conflicts
0xbbee74c2…567a
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: 0x065c9d28…a9c394
1 conflict on slot 0x000761bdaf…52734d
Audit this contract →
← previous block·next block →recent activity