pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,979,648
10 transactions · 8 stateful · 2026-05-07 07:29:03 UTC
Parallelism
70/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,979,648 · 10 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
1w03w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0x70b2f813…783c
0x2a68ba…90c5
4 touches
1 conflict
0x3a91a616…dec4
0x065c9d…c394
3 touches
1 conflict
0x18aed20c…48f3
0x000000…012a
2 touches
0 conflicts
0xeda2edc3…91d8
0x000000…012a
2 touches
0 conflicts
0x33018431…8f5c
0x188d58…ea8e
2 touches
0 conflicts
0x33018431…8f5e
0x188d58…ea8e
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity