pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,919,871
14 transactions · 12 stateful · 2026-05-16 07:11:55 UTC
Parallelism
79/100
Blocked
25%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,919,871 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w010w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba38536d…2b7d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xa6ec1494…c344
0x065c9d…c394
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xda98819b…21ce
0x065c9d…c394
3 touches
1 conflict
0xe5035474…567c
0x065c9d…c394
3 touches
1 conflict
0x801d89fc…cded
0x065c9d…c394
3 touches
1 conflict
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
3 conflicts on slot 0xba38536db1…342b7d
Audit this contract →
← previous block·next block →recent activity