← previous blocknext block →recent activity
Analyzing
Block #74,795,744
13 transactions · 12 stateful · 2026-05-15 17:24:05 UTC
Parallelism
85/100
Blocked
25%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,795,744 · 13 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
2w03w04w18w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x85a88798…f85e
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0xba809423…9b52
0x065c9d…c394
2 touches
0 conflicts
0xcaa75598…b6c6
0x065c9d…c394
2 touches
0 conflicts
0x866bf367…7a60
0x188d58…ea8e
2 touches
0 conflicts
0x866bf367…7a61
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: Perpl
1 conflict on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity