pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,399,983
16 transactions · 11 stateful · 2026-05-04 15:07:06 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,399,983 · 16 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
1w03w04w17w08w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0x7e9d3a…9fda
4 touches
1 conflict
0x8a7dccab…0f1c
0x2a68ba…90c5
2 touches
1 conflict
0x08fdbdc9…aa7c
0x065c9d…c394
2 touches
0 conflicts
0x1c933fb1…0949
0x065c9d…c394
2 touches
0 conflicts
0x6bbe7a63…4500
0x065c9d…c394
2 touches
0 conflicts
0x8a2a7a38…01bf
0x065c9d…c394
2 touches
0 conflicts
0x92e544e2…ce1b
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity