← previous blocknext block →recent activity
Analyzing
Block #74,427,729
34 transactions · 26 stateful · 2026-05-14 00:23:10 UTC
Parallelism
85/100
Blocked
46%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,427,729 · 34 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w18w09w115w216w018w120w022w123w226w128w230w331w432w233w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbad68552…e6bf
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xbbee74c2…567a
0x065c9d…c394
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x06db03a6…4692
0x34b655…2a6f
4 touches
1 conflict
0x157d1e46…85f6
0x34b655…2a6f
4 touches
1 conflict
0x4582e32d…1abe
0x34b655…2a6f
4 touches
1 conflict
0x5f450515…3bc4
0x34b655…2a6f
4 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: Perpl
6 conflicts on slot 0xbad6855239…f0e6bf
Audit this contract →
← previous block·next block →recent activity